General clarifications and improvements
Opened this issue · 0 comments
Original internal issue to consider the following improvements and clarifications for the following paragraphs in the specification:
2.1 The design principles are not numbered which makes it harder to refer to.
2.6.4 At this stage of reading the protocol it is very unclear what this paragraph says. It seems as if it talks about a different layer of the system not directly relevant of the Whiteflag protocol. Makes the document confusing.
2.7 This paragraph feels as it is intended to help, but it only confuses because at this stage only the message characters are introduced, and the given examples are not understandable. Please add a human readable text what for example E01 or D10(5)X means.
4.1.3 The term ‘compression’ is not correct. I think it is clearer if the definition of the messages and the mapping to the underlying blockchain is separated. I assume that with ‘compression’ the mapping to a given blockchain is meant. Also, it assumes that the mapping for any blockchain is always the same.
4.2.1 Why is there a separate column with ‘compressed encoding’. Is the encoding different per field or just as described in 4.1.3?
4.3.1.1 n means ?
4.3.1.1 _ means +/- ?
5.1.1 This seems to imply that multisig / deterministic addresses can’t be used. However, no requirements on the used addresses are mentioned.
5.1.1 The sequence A(0), message X, A(1) means that message X in fact should be ignored because A(1) recalls the original A(0) as if it never happens?