Expand description
TOML test-vector parser.
A TestVector is the unit NIST hands to the harness: a scheme
name, the test parameters (parties, threshold, message, RNG seed),
optional expected-output bytes, and a list of per-party Byzantine
behaviors.
The schema matches TODO.roadmap/09-nist-evaluation-harness.md:
[scheme]
name = "FROST-ed25519"
version = "draft-irtf-cfrg-frost-13"
[test]
parties = 5
threshold = 3
message = "hello world" # UTF-8 string OR "0x.."
seed = "0xdeadbeef..." # hex seed for deterministic RNG
expected_signature_hex = "..." # optional
conformance_level = "must_pass" # must_pass | should_pass | informational
reference = "https://..." # normative spec URL
expected_round_count = 3 # warn if observed differs
share_material = "nist-dkg-set-A" # named pre-shared share label
[[peer_behavior]]
party_id = "alice"
type = "honest"Structs§
- Peer
Behavior Entry - One
[[peer_behavior]]entry. - Scheme
Spec [scheme]block: identity of the candidate under test.- Test
Vector - Top-level TOML document.
- Test
Vector Test [test]block: harness inputs.
Enums§
- Conformance
Level - Conformance level declared by a vector. Mirrors NIST’s
MUST/SHOULD/INFORMATIONAL classification: a
MustPassfailure is a hard error; aShouldPassfailure is a warning (the scheme is expected to comply but the failure is not disqualifying on its own);Informationalfailures never count against the candidate.