Re: [Bitcoin-development] To prevent arbitrary data storage in txouts — The Ultimate Solution

2013-04-10 Thread Jorge Timón
On 4/10/13, Peter Todd wrote: > Oh, and while we're at it, long-term (hard-fork) it'd be good to change > the tx hash algorithm to extend the merkle tree into the txouts/txins > itself, which means that to prove a given txout exists you only need to > provide it, rather than the full tx. > > Curre

Re: [Bitcoin-development] bitcoinj 0.8

2013-04-10 Thread Mike Hearn
The key in the message was used in my last announcement, so that establishes continuity there. But regardless, all mails I send are signed automatically by Gmail using either the gmail.com consumer key (for my posts to this list) or the google.com corporate key (for my posts to the bitcoinj lists)

Re: [Bitcoin-development] bitcoinj 0.8

2013-04-10 Thread Andy Parkins
On Tuesday 09 April 2013 22:03:35 Mike Hearn wrote: > To get bitcoinj 0.8, check out our source from git and then run *git fetch > --all; git checkout **cbbb1a2bf4d1*. This will place you on the 0.8 release > in a secure manner. This message was written on Tuesday 9th April 2013 and Not quite sec

Re: [Bitcoin-development] To prevent arbitrary data storage in txouts — The Ultimate Solution

2013-04-10 Thread Peter Todd
On Wed, Apr 10, 2013 at 12:15:26AM -0700, Gregory Maxwell wrote: > On Tue, Apr 9, 2013 at 11:53 PM, Peter Todd wrote: > > Of course, either way you have the odd side-effect that it's now > > difficult to pay further funds to a random txout seen on the > > blockchain... strange, although possibly n

Re: [Bitcoin-development] To prevent arbitrary data storage in txouts — The Ultimate Solution

2013-04-10 Thread Gregory Maxwell
On Tue, Apr 9, 2013 at 11:53 PM, Peter Todd wrote: > Of course, either way you have the odd side-effect that it's now > difficult to pay further funds to a random txout seen on the > blockchain... strange, although possibly not a bad thing. Oh wow, thats actually a quite good thing— it's a proper