📅 Original date posted:2015-06-15
📝 Original message:Mark Friedenbach <mark at friedenbach.org> writes:
> There's another important use case which you mentioned Greg, that also
> requires special exemption: compact commitments via mid-state compression.
>
> The use case is an OP_RETURN output sorted last, whose last N bytes are a
> commitment of some kind. A proof of the commitment can then use mid state
> compression to elide the beginning of the transaction.
>
> How do you make a special exemption for this category of outputs? I can't
> think of a very clean way of doing so that doesn't require an ugly
> advertising of sort-order exemptions.
Yes, we can suit any one use case, but not all of them.
For example, outputs shall be sorted by:
1. First byte (or 0 if script is zero length) minus 107.
2. The remainder of the script in lexographical order.
This would put OP_RETURN outputs last.
Though Peter Todd's more general best-effort language might make more
sense. It's not like you can hide an OP_RETURN transaction to make it
look like something else, so that transaction not going to be
distinguished by non-canonical ordering.
Cheers,
Rusty.
Rusty Russell [ARCHIVE] /
npub1zw…hkhpx
2023-06-07 15:36:44
in reply to nevent1q…0aq2
Author Public Key
npub1zw7cc8z78v6s3grujfvcv3ckpvg6kr0w7nz9yzvwyglyg0qu5sjsqhkhpxPublished at
2023-06-07 15:36:44Event JSON
{
"id": "4acc9c1c11bda679dd3af73607301e0303e094f4fc79d631d2a29d6b6b780ed0",
"pubkey": "13bd8c1c5e3b3508a07c92598647160b11ab0deef4c452098e223e443c1ca425",
"created_at": 1686152204,
"kind": 1,
"tags": [
[
"e",
"981f41da2a008fa33b1384e8dd3f0d4a96b7f3bed5c463f00f9032a495226e9c",
"",
"root"
],
[
"e",
"d727772edf0ba256b0aa154b015504a47fbd85074ad00e40fb427b65a51021b0",
"",
"reply"
],
[
"p",
"1c61d995949cbfaf14f767784e166bde865c7b8783d7aa3bf0a1d014b70c0069"
]
],
"content": "📅 Original date posted:2015-06-15\n📝 Original message:Mark Friedenbach \u003cmark at friedenbach.org\u003e writes:\n\u003e There's another important use case which you mentioned Greg, that also\n\u003e requires special exemption: compact commitments via mid-state compression.\n\u003e\n\u003e The use case is an OP_RETURN output sorted last, whose last N bytes are a\n\u003e commitment of some kind. A proof of the commitment can then use mid state\n\u003e compression to elide the beginning of the transaction.\n\u003e\n\u003e How do you make a special exemption for this category of outputs? I can't\n\u003e think of a very clean way of doing so that doesn't require an ugly\n\u003e advertising of sort-order exemptions.\n\nYes, we can suit any one use case, but not all of them.\n\nFor example, outputs shall be sorted by:\n 1. First byte (or 0 if script is zero length) minus 107.\n 2. The remainder of the script in lexographical order.\n\nThis would put OP_RETURN outputs last.\n\nThough Peter Todd's more general best-effort language might make more\nsense. It's not like you can hide an OP_RETURN transaction to make it\nlook like something else, so that transaction not going to be\ndistinguished by non-canonical ordering.\n\nCheers,\nRusty.",
"sig": "6d33ba91433e4b99620be1cc248f069ded4fc68e4f5fcf51bf56376aa20a2dbb1218f68fd4aefad4fe117af195e18dc5b165464b59d8d6340eb9a09ea38b074a"
}