vectors: add L0 conformance corpus + spec reference#275
Open
topocount wants to merge 1 commit into
Open
Conversation
Adds a versioned, checked-in set of golden conformance vectors for the message cryptographic layer (canonical data_bytes serialization, BLAKE3-160 hash, Ed25519 signature, signer), generated by the reference implementation (farcasterxyz/snapchain) and mirrored here as the cross-client source of truth for FIP validator-onboarding gate L0. - vectors/v1/: manifest.json (hex of every field + semantic input) plus messages/<id>.pb (authoritative wire bytes) and messages/<id>.pb.txt (reviewable wire disassembly). 10 message types. - vectors/README.md: corpus format + the language-agnostic verification algorithm (verify hash/signature against the carried data_bytes; do not re-encode, since protobuf serialization is not canonical across impls). - SPECIFICATION.md §2: a "Conformance Vectors" subsection pointing at them. Post-state merkle roots are intentionally omitted: §4.2's trie spec is stale relative to the reference implementation's sharded trie. Reconciling that (and then adding state-root vectors) is tracked separately.
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
1 participant
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.
Adds a versioned, checked-in set of golden conformance vectors for the
message cryptographic layer (canonical data_bytes serialization, BLAKE3-160
hash, Ed25519 signature, signer), generated by the reference implementation
(farcasterxyz/snapchain) and mirrored here as the cross-client source of
truth for FIP validator-onboarding gate L0.
messages/.pb (authoritative wire bytes) and messages/.pb.txt
(reviewable wire disassembly). 10 message types.
algorithm (verify hash/signature against the carried data_bytes; do not
re-encode, since protobuf serialization is not canonical across impls).
Post-state merkle roots are intentionally omitted: §4.2's trie spec is
stale relative to the reference implementation's sharded trie. Reconciling
that (and then adding state-root vectors) is tracked separately.