📅 Original date posted:2014-05-03
📝 Original message:On Sat, May 3, 2014 at 11:55 AM, Mark Friedenbach <mark at monetize.io> wrote:
> I don't think such a pull request would be accepted. The point was to
> minimize impact to the block chain. Each extras txout adds 9 bytes
> minimum, with zero benefit over serializing the data together in a
> single OP_RETURN.
In this case it's not a question extra txouts, its a question of
additional pushes. Assuming you didn't get the push overhead for free,
the only issue I see with that off the cuff is extra complexity in the
IsStandard rule... but really, why? Your application already needs to
define the meaning of the data— what point is there in making your
hash commitment less uniform with the rest of the network?
Gregory Maxwell [ARCHIVE] /
npub1f2…crwet
2023-06-07 15:20:54
in reply to nevent1q…nnq3
Author Public Key
npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwetPublished at
2023-06-07 15:20:54Event JSON
{
"id": "402585ba3634bbd87396f02be98151f96d0e77b7958328428b7c347474e61335",
"pubkey": "4aa6cf9aa5c8e98f401dac603c6a10207509b6a07317676e9d6615f3d7103d73",
"created_at": 1686151254,
"kind": 1,
"tags": [
[
"e",
"16e41fd8d1a66d26890ffeb755f22e3a8eb1c8b9debfb4782bf4946f5773a9bc",
"",
"root"
],
[
"e",
"f268f60bbfc96d6e44089287f413efa18f7a7e9c4507b4c79ac3e4588deb3438",
"",
"reply"
],
[
"p",
"1c61d995949cbfaf14f767784e166bde865c7b8783d7aa3bf0a1d014b70c0069"
]
],
"content": "📅 Original date posted:2014-05-03\n📝 Original message:On Sat, May 3, 2014 at 11:55 AM, Mark Friedenbach \u003cmark at monetize.io\u003e wrote:\n\u003e I don't think such a pull request would be accepted. The point was to\n\u003e minimize impact to the block chain. Each extras txout adds 9 bytes\n\u003e minimum, with zero benefit over serializing the data together in a\n\u003e single OP_RETURN.\n\nIn this case it's not a question extra txouts, its a question of\nadditional pushes. Assuming you didn't get the push overhead for free,\nthe only issue I see with that off the cuff is extra complexity in the\nIsStandard rule... but really, why? Your application already needs to\ndefine the meaning of the data— what point is there in making your\nhash commitment less uniform with the rest of the network?",
"sig": "642eb5bdbe5ac8556f1e44dc2f6d1d3b01bf1349012124cc8f8a52020b3ed7a98fce769f1890b81403afc1720522d3ed2411d6415481ef69b853e29d2cdb3da5"
}