{"type":"rich","version":"1.0","author_name":"npub1k2eekmevs6gg60df75qpjw4a2atmy89vx28c8zqq5jxy64tuzrws39qd6m","author_url":"https://nostr.ae/npub1k2eekmevs6gg60df75qpjw4a2atmy89vx28c8zqq5jxy64tuzrws39qd6m","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-12-08\n📝 Original message:On 12/08/2015 09:12 AM, Gavin Andresen via bitcoin-dev wrote:\n\u003e Stuffing the segwitness merkle tree in the coinbase\n\nIf such a change is going to be deployed via a soft fork instead of a\nhard fork, then the coinbase is the worst place to put the segwitness\nmerkle root.\n\nInstead, put it in the first output of the generation transaction as an\nOP_RETURN script.\n\nThis is a better pattern because coinbase space is limited while output\nspace is not. The next time there's a good reason to tie another merkle\ntree to a block, that proposal can be designated for the second output\nof the generation transaction.\n\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: 0xEAD9E623.asc\nType: application/pgp-keys\nSize: 23337 bytes\nDesc: not available\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20151208/a7f58417/attachment-0001.bin\u003e\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 801 bytes\nDesc: OpenPGP digital signature\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20151208/a7f58417/attachment-0001.sig\u003e"}
