Transaction and Signatures pages lack information on field ordering and encoding requirements

[FrankSzendzielarz]

Describe the error The Transaction reference and structure pages, and Signature page, omit that transaction field ordering is important for computing the signature and transaction id. Field ordering is not important for the Transaction message POSTed to the network however.

Link to the page or line Transactions page

Optional - The recommended fix if you have one Dedicated info on how to form the message, with a 'canonical messagepack' encoding for signature/id computation.

[FrankSzendzielarz]

Hi there @kelvinDev67 thanks, I don't need to - I've been talking already on Discord. My feedback is that the docs lack that information. If there is going to be information about manual transaction construction and transaction structure, then in it's present form it is incomplete.