{"type":"rich","version":"1.0","author_name":"npub1r3san9v5njl6798hvauyu9ntm6r9c7u8s0t65wls58gpfdcvqp5sa48d0u","author_url":"https://nostr.ae/npub1r3san9v5njl6798hvauyu9ntm6r9c7u8s0t65wls58gpfdcvqp5sa48d0u","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-12-08\n📝 Original message:A far better place than the generation transaction (which I assume means\ncoinbase transaction?) is the last transaction in the block. That allows\nyou to save, on average, half of the hashes in the Merkle tree.\n\nOn Tue, Dec 8, 2015 at 11:55 PM, Justus Ranvier via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e On 12/08/2015 09:12 AM, Gavin Andresen via bitcoin-dev wrote:\n\u003e \u003e Stuffing the segwitness merkle tree in the coinbase\n\u003e\n\u003e If such a change is going to be deployed via a soft fork instead of a\n\u003e hard fork, then the coinbase is the worst place to put the segwitness\n\u003e merkle root.\n\u003e\n\u003e Instead, put it in the first output of the generation transaction as an\n\u003e OP_RETURN script.\n\u003e\n\u003e This is a better pattern because coinbase space is limited while output\n\u003e space is not. The next time there's a good reason to tie another merkle\n\u003e tree to a block, that proposal can be designated for the second output\n\u003e of the generation transaction.\n\u003e\n\u003e\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20151209/040dbf84/attachment.html\u003e"}