📅 Original date posted:2018-11-15
📝 Original message:
Conner Fromknecht <conner at lightning.engineering> writes:
>> For a sequence of `type,len,value`, the `type`s must be in ascending order
>> -- not explicitly accepted or rejected. It would be easier to check
>> uniqueness > (the previous rule we accepted) here for a naive parser (keep
>> track of some "minimum allowed type" that initializes at zero, check current
>> type >= this, update to current type + 1) if `type`s are in ascending order.
>
> Yep ascending makes sense to me, for the reasons you stated.
Definitely a good idea, especially because it results in a canonical
serialization format, which is important to ensure signatures over
messages can be verified even when reserializing parsed messages.
Christian Decker [ARCHIVE] /
npub1wt…gtuyn
2023-06-09 12:52:54
in reply to nevent1q…6zrg
Author Public Key
npub1wtx5qvewc7pd6znlvwktq03mdld05mv3h5dkzfwd3dc30gdmsptsugtuynPublished at
2023-06-09 12:52:54Event JSON
{
"id": "f0653130a944fa7c54982782a0aa3ab47bfe3aa16b3ac6f134ab08436207628c",
"pubkey": "72cd40332ec782dd0a7f63acb03e3b6fdafa6d91bd1b6125cd8b7117a1bb8057",
"created_at": 1686315174,
"kind": 1,
"tags": [
[
"e",
"d96b54bd1a16a00379a91b3db2449979b8b41d8eecbbb0fb0270247887f2b600",
"",
"root"
],
[
"e",
"0cfda0c012738f6c337d8d6940d961b9764c243af07de69fffcb1885bf39802b",
"",
"reply"
],
[
"p",
"175fd2f52497b9ba272cebdb436ee9876f111b6aa2af3ea9bc03e7cdf4b45246"
]
],
"content": "📅 Original date posted:2018-11-15\n📝 Original message:\nConner Fromknecht \u003cconner at lightning.engineering\u003e writes:\n\u003e\u003e For a sequence of `type,len,value`, the `type`s must be in ascending order\n\u003e\u003e -- not explicitly accepted or rejected. It would be easier to check\n\u003e\u003e uniqueness \u003e (the previous rule we accepted) here for a naive parser (keep\n\u003e\u003e track of some \"minimum allowed type\" that initializes at zero, check current\n\u003e\u003e type \u003e= this, update to current type + 1) if `type`s are in ascending order.\n\u003e\n\u003e Yep ascending makes sense to me, for the reasons you stated.\n\nDefinitely a good idea, especially because it results in a canonical\nserialization format, which is important to ensure signatures over\nmessages can be verified even when reserializing parsed messages.",
"sig": "0111c6f4dd84eb8d87ca118aa0a00f6a6861eb03daa58feaaf6cc6d4d40c1c783b037f45568bde6dcd9d7e849385dfbf849f695ea1d4d20ff27dcc0aac428e32"
}