rich1.0npub1k2eekmevs6gg60df75qpjw4a2atmy89vx28c8zqq5jxy64tuzrws39qd6mhttps://nostr.ae/npub1k2eekmevs6gg60df75qpjw4a2atmy89vx28c8zqq5jxy64tuzrws39qd6mnjumphttps://nostr.ae📅 Original date posted:2015-12-08 📝 Original message: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. -------------- next part -------------- A non-text attachment was scrubbed... Name: 0xEAD9E623.asc Type: application/pgp-keys Size: 23337 bytes Desc: not available URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20151208/a7f58417/attachment-0001.bin> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20151208/a7f58417/attachment-0001.sig>