Gregory Maxwell [ARCHIVE] on Nostr: 📅 Original date posted:2014-05-03 📝 Original message:On Sat, May 3, 2014 at ...
📅 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?
📝 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?