Open
Conversation
Slight adjustment to the wording in the first Process sentence; changed "an" to "a" for secp256k1 public key; added Standards for Efficient Cryptography for first SEC usage in section.
parasyte
reviewed
Jan 19, 2026
| single prefix byte (`0x02` or `0x03`) followed by the 32-byte x-coordinate of | ||
| the elliptic curve point. | ||
| A secp256k1 public key can be used as the [Genesis Bytes]. The key MUST be | ||
| in its compressed Standards for Efficient Cryptography (SEC) format: a 33-byte |
Collaborator
There was a problem hiding this comment.
Same comment wrt. citing SEC 2 as in #289 (review)
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Slight adjustment to the wording in the first Process sentence; changed "an" to "a" for secp256k1 public key; added Standards for Efficient Cryptography for first SEC usage in section.