š
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>;
Justus Ranvier [ARCHIVE] /
npub1k2ā¦9qd6m
2023-06-07 17:45:37
in reply to nevent1qā¦86m6
Author Public Key
npub1k2eekmevs6gg60df75qpjw4a2atmy89vx28c8zqq5jxy64tuzrws39qd6mPublished at
2023-06-07 17:45:37Event JSON
{
"id": "d7ae422c302a7e5c36dda073d3e2a6874562093a4f15b7503582f7ed3c5462df",
"pubkey": "b2b39b6f2c86908d3da9f500193abd5757b21cac328f838800a48c4d557c10dd",
"created_at": 1686159937,
"kind": 1,
"tags": [
[
"e",
"558b0da1f3869961bbef0556878e1dd6b9ae37e86128bc130bab17f5332c918d",
"",
"root"
],
[
"e",
"322912e5797a4e6be5b9d41dac63db3b9ac81be08d48cffe3ebae904d259a47b",
"",
"reply"
],
[
"p",
"857f2f78dc1639e711f5ea703a9fc978e22ebd279abdea1861b7daa833512ee4"
]
],
"content": "š
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",
"sig": "d6b8de58c01710344583e7df7c010f5c63240588e8f2b36469f1af47ebcae25cc000eda8ee1b573e4f740caef99a7b14bae447644cb1507bc3477dde89254b57"
}