Am Mo, 24.10.2011, 16:55, schrieb Gavin Andresen: > Green addresses could be implemented as a second signature in the > scriptSig. You'd have to hack your bitcoin client, but you could > generate a transaction that had <greensig> <sig> <pubKey> ... as the > input instead of <sig> <pubKey>. > > The <greensig> will be ignored by old clients. The transactions is > still considered 'standard'. But you could teach bitcoin to look for > <greensig> signatures in wallet transactions...
I played around with this a little bit and managed to generate such transactions. However, I ran into the problem that IsStandard() also checks that the size of scriptSig is not above 200. Adding an extra signature there triggers this limit. I guess there is no way around that? Regards, Jan ------------------------------------------------------------------------------ The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
