Re: [Bitcoin-development] Version 0.6 release candidate 1 plan
On Monday, February 06, 2012 10:54:25 AM Luke-Jr wrote: 769 : Make transactions with extra data in scriptSig non-standard If this affects relaying, it will significantly harm the ability to replace the current spammy green address scheme with a sensible extra signature system. On the miner end, it could significantly harm adoption of such a system. FWIW, at least MtGox was OK with the plan to move to non-blockchain-spam 0-confirmation via an extra signature. Why do you ignore this possibility, and merge stuff that will break it? Do you have an alternative solution to the problem of green addresses spamming the blockchain? As I noted in the pull request, stripping extra data has no negative impact on normal transactions, and clients creating these can be written to expect the txnid to change (or simply not care what the txnid is). -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] Version 0.6 release candidate 1 plan
On Tuesday, February 07, 2012 10:04:36 AM Luke-Jr wrote: On Monday, February 06, 2012 10:54:25 AM Luke-Jr wrote: 769 : Make transactions with extra data in scriptSig non-standard If this affects relaying, it will significantly harm the ability to replace the current spammy green address scheme with a sensible extra signature system. On the miner end, it could significantly harm adoption of such a system. gmaxwell explained to me why this is no longer needed on IRC. I withdraw my objection. -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] Version 0.6 release candidate 1 plan
Do you have an alternative solution to the problem of green addresses spamming the blockchain? Sure, here's one: Green address provider give a REST-ful API, that provides the following functionality: + Give transaction ID and credentials, request that the transaction be declared green (sender's wallet site/software would do this) + Give transaction ID, return boolean has this transaction been deeclared green? As I said, I think any design that relies on clients recognizing two variations of a transaction is a very bad idea. -- -- Gavin Andresen -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
[Bitcoin-development] Version 0.6 release candidate 1 plan
There are several major changes in git HEAD that are ready for wider testing. The best way of getting lots of testing is to release binaries, so I'm going to be pulling together a release candidate in the next day or two. The goal will be to get at least a full month of release candidate review/testing before releasing a 0.6 final, with zero High Priority bugs ( https://github.com/bitcoin/bitcoin/issues?labels=Priority+Highstate=open ) Here's the proposed TODO list for a rc1: Pull: 800 : bug fix, multiple output display fix in GUI 799 : Have bitcoind recomend a secure RPC password 769 : Make transactions with extra data in scriptSig non-standard Rebase/pull: 795 : Fix minimize to tray Pull a modified version of: 755 : Don't vote for /P2SH/ unless -p2sh specified I'd like to pull 787 (CAddrMan: stochastic address manager) but it didn't pass my sanity tests. I'm going to start a separate discussion thread with some thoughts on rolling out higher-level multisignature support. -- -- Gavin Andresen -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
