You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the file docs/learn/operation-format-execution.mdx, for the explanation of the checksum verification, the doc says :
- serialize the operation ID in binary format (see above)
- compute the SHA256 hash of the binary serialization
- append the first 4 bytes of the sha256 hash at the end of the binary serialization of the ID. This is used as a checksum to detect typing errors as operation IDs are also meant to be written on paper by humans.
In reality it is :
- compute the SHA256 hash of the SHA256 hash of the binary serialization
The serialization of the binary => A
Computing sha256(sha256(A)
the first 4 bytes of this result are appended at the end of the binary serialization (A).
This process is present many time on the document.
Thanks for the correction
The text was updated successfully, but these errors were encountered:
Hello
On the file docs/learn/operation-format-execution.mdx, for the explanation of the checksum verification, the doc says :
- serialize the operation ID in binary format (see above)
- compute the SHA256 hash of the binary serialization
- append the first 4 bytes of the sha256 hash at the end of the binary serialization of the ID. This is used as a checksum to detect typing errors as operation IDs are also meant to be written on paper by humans.
In reality it is :
- compute the SHA256 hash of the SHA256 hash of the binary serialization
The serialization of the binary => A
Computing sha256(sha256(A)
the first 4 bytes of this result are appended at the end of the binary serialization (A).
This process is present many time on the document.
Thanks for the correction
The text was updated successfully, but these errors were encountered: