Re: [Bitcoin-development] Large backlog of transactions building up?
On Tue, Sep 25, 2012 at 1:34 PM, Jorge Timón timon.elvi...@gmail.com wrote: On 9/23/12, Jeff Garzik jgar...@exmulti.com wrote: - provides a deterministic lifetime for a TX; if you KNOW a TX will disappear 144 blocks (24 hours) after you stop transmitting, then it is probably safe to initiate recovery procedures and perhaps revise the transaction - prevents zombie TXs from littering memory... they hang around, wasting resources, but never get confirmed I don't understand. Can the chain enforce this number? Why can't clients delete all those transactions right now? This is discussion about transactions which are not in the chain yet. On 9/23/12, Gregory Maxwell gmaxw...@gmail.com wrote: There are bursts of weird transactions (e.g. someone was flooding zero value txn a few weeks ago; before that there were some enormous series of double-spend induced orphans), and other sustained loads that quite a few miners are intentionally excluding. Why clients store transactions that don't obey the current rules of the chain at all? The double spending transaction is not stored— which is, in fact, the problem which creates these huge chain. When a transaction depending on the doublespend is received we do not know its parent (because we dropped it because it was a rule violation) so we keep it around as an orphan hoping its parent arrives. The software could maintain a cache of rejected txids to consult for orphan txn's parents, but it would need to be dropped any time there is a reorg so I don't know how useful it would be. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
[Bitcoin-development] Bitcoin Testing Project
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi All, After the failure to get any real testing done for the 0.7 release (all of which is my fault) I have decided to rejig things. I am heavily into test driven development, and I have a strong background in requirements management, and automation. I want to leave bettermeans behind, maybe we might be able to keep the voting aspect of it, and link it into mantis. So, what I have been doing over the past few weeks is developing a rudimentary requirements set, basic requirement tracking, tests to prove/stress the requirements. The next most important thing is to get release/acceptance tests done - these primarily focus on new stuff doesnt break old (ie lose a wallet, etc) and needs no special requirements. To this end I have installed various opensource applications (mantis, salomeTMF, bugzilla, etc) and am currently evaluating the best workflow process. This was a much longer post, but decided against it. :) So, what I want to know is who wants to be a part helping me out with all this? I am finalising the workflow flow diagrams and they should be ready for inspection soon. Anyone interested in helping out/reviewing processes? even if it is just some encouragement, it is all greatly appreciated. Drop me an email if you want access to the current setup and help me review the different software for the bitcoin workflow process. cheers, steve - -- my PGP public key is at pgp.mit.edu id: 0x5016FB50 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQEcBAEBAgAGBQJQYfjMAAoJEFvEB9dQFvtQSmsH/R/FEdOQRB7ncTnHhaP8woLu nIiGX2DgLOWLOF9launSuTCrtVm2G56B9Dgl/BqScFxeuJGbzje7+kp7LgjtA3uy kS9DUZ1zhUfhslGP0UpVJJGX6Yfk8GbQ4nUcuL1VTv6nSZXWP2EvLMDPpRgKwyi5 z1FiyBg2A3Kg3Er+VmHPmpI0zZAGB5ytaenUp4xXGhL7Nk66i5X0twVr51xlEm0L zKCDXHzWTvNNlT7TzMjIxShJ/EcgCI1r6tVD3T+2e9QeVm0QNw3xeNUkMxKn+ul8 d1v1OxJbHD1CsNqW+XgVvFE2SJReizaHNOFwrqcpVCp7bABnWAB5eyTzB9B9IX8= =di5x -END PGP SIGNATURE- -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] Bitcoin Testing Project
Although Jenkins may not be the best system, we already have jenkins and pull-tester (which is a dumb python script I wrote to test all incoming pull requests from github). They both run the same set of scripts, namely those at https://github.com/TheBlueMatt/test-scripts (its pretty basic right now, but since it is on github, I was hoping someone would find the inspiration to add to it). I dont really care if we keep using jenkins, but I figure we might as well keep all the tests in one place? Anyway, I'm all for more testing (I'm always complaining about how we need more tests for stuff...). Matt On Tue, 2012-09-25 at 19:32 +0100, steve wrote: Hi All, After the failure to get any real testing done for the 0.7 release (all of which is my fault) I have decided to rejig things. I am heavily into test driven development, and I have a strong background in requirements management, and automation. I want to leave bettermeans behind, maybe we might be able to keep the voting aspect of it, and link it into mantis. So, what I have been doing over the past few weeks is developing a rudimentary requirements set, basic requirement tracking, tests to prove/stress the requirements. The next most important thing is to get release/acceptance tests done - these primarily focus on new stuff doesnt break old (ie lose a wallet, etc) and needs no special requirements. To this end I have installed various opensource applications (mantis, salomeTMF, bugzilla, etc) and am currently evaluating the best workflow process. This was a much longer post, but decided against it. :) So, what I want to know is who wants to be a part helping me out with all this? I am finalising the workflow flow diagrams and they should be ready for inspection soon. Anyone interested in helping out/reviewing processes? even if it is just some encouragement, it is all greatly appreciated. Drop me an email if you want access to the current setup and help me review the different software for the bitcoin workflow process. cheers, steve -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] Bitcoin Testing Project
on 09/25/2012 02:32 PM steve said the following: Anyone interested in helping out/reviewing processes? even if it is just some encouragement, it is all greatly appreciated. not enough time in the day for me to seriously help out, but since you asked, here's some encouragement. :) more testing == good. signature.asc Description: OpenPGP digital signature -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] Bitcoin Testing Project
This is definitely worth doing and I wish you every encouragement. For my part I'm working on a different area of the Bitcoin ecosystem and that is taking up all my time so I can only cheer you on from the sidelines. On 25 September 2012 21:49, Daniel F nanot...@gmail.com wrote: on 09/25/2012 02:32 PM steve said the following: Anyone interested in helping out/reviewing processes? even if it is just some encouragement, it is all greatly appreciated. not enough time in the day for me to seriously help out, but since you asked, here's some encouragement. :) more testing == good. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] Bitcoin Testing Project
I think it's a great initiative Steve, On Tue, Sep 25, 2012 at 10:41 PM, Matt Corallo bitcoin-l...@bluematt.me wrote: They both run the same set of scripts, namely those at https://github.com/TheBlueMatt/test-scripts (its pretty basic right now, but since it is on github, I was hoping someone would find the inspiration to add to it). The pulltester and Jenkins are really useful, I think it's best to keep these and improve them if needed. I dont really care if we keep using jenkins, but I figure we might as well keep all the tests in one place? Which brings me to another issue: we desperately need a page that links all the developer resources for bitcoin dev: - link to my doxygen docs (https://dev.visucore.com/bitcoin/doxygen/) - bluematt's pulltester and jenkins - any testing dashboards Steve is going to add But also: - how to check out the source code, how to find the build instructions for your platform - contribution guidelines - where to ask w/ development problems (this mailing list, #bitcoin-dev) - where to begin, which bugs to solve first ... Maybe on bitcoin.org, but at least easy to find for people that want to contribute, not just some deeply nested wiki page. Ie, something like https://www.mozilla.org/en-US/contribute/ http://www.ogre3d.org/developers ... I'm willing to write this. But I know these kinds of proposals always end in a big discussion about what should be and what should not be on bitcoin.org, however we should be a bit pragmatic here. Wladimir -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
