type,len,value standard



Summary:

The conversation is about the sequence of `type, len, value`. The speaker suggests that the `type`s should be in ascending order for a naive parser. He suggests to keep track of some "minimum allowed type" that initializes at zero and update to current type +1 to check current type >= this. It will make checking uniqueness easier for a naive parser. The other person agrees with the suggestion as it results in a canonical serialization format. This format is important to ensure signatures over messages can be verified even when reserializing parsed messages.


Updated on: 2023-05-25T17:05:54.534288+00:00