rich1.0npub1r3san9v5njl6798hvauyu9ntm6r9c7u8s0t65wls58gpfdcvqp5sa48d0uhttps://nostr.ae/npub1r3san9v5njl6798hvauyu9ntm6r9c7u8s0t65wls58gpfdcvqp5sa48d0unjumphttps://nostr.ae📅 Original date posted:2015-12-08 📝 Original message:A far better place than the generation transaction (which I assume means coinbase transaction?) is the last transaction in the block. That allows you to save, on average, half of the hashes in the Merkle tree. On Tue, Dec 8, 2015 at 11:55 PM, Justus Ranvier via bitcoin-dev < bitcoin-dev at lists.linuxfoundation.org> wrote: > On 12/08/2015 09:12 AM, Gavin Andresen via bitcoin-dev wrote: > > Stuffing the segwitness merkle tree in the coinbase > > If such a change is going to be deployed via a soft fork instead of a > hard fork, then the coinbase is the worst place to put the segwitness > merkle root. > > Instead, put it in the first output of the generation transaction as an > OP_RETURN script. > > This is a better pattern because coinbase space is limited while output > space is not. The next time there's a good reason to tie another merkle > tree to a block, that proposal can be designated for the second output > of the generation transaction. > > > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20151209/040dbf84/attachment.html>