Expand description
v16 request-proof signer enrollment manifest (design §4.4, §11).
Request-proof signer keys are their own enrollment, with their own lifecycle. They are deliberately not derived from, and never shared with, the mesh/envelope identity: component-key separation is normative, so a key enrolled for the request-proof WNS hybrid suite MUST NOT simultaneously be enrolled for another protocol or domain separator. Relabelling the mesh Ed25519 + ML-DSA-65 pair as a proof signer would be exactly that violation, and it could not supply an enrollment epoch, validity window, revocation state, approver role, or enrollment-policy identifier either — those are enrollment facts, not transport facts, and inventing them is not enrollment.
The manifest is an operator-authored file, established out-of-band like the other admin-anchored trust material. Absent manifest, nothing is enrolled and every authenticated proof denies; there is no derived fallback.
Cross-protocol overlap is checked, not merely documented: an entry whose component key is already anchored as a mesh/envelope identity is rejected unless the entry names an explicit operator-approved exception policy.
Structs§
- Manifest
Component - One pinned component key: its key ID and its public key material.
- Manifest
Entry - One enrolled signer in the manifest.
- Proof
Enrollment Manifest - The manifest file.
Enums§
- Manifest
Alg - Manifest
Role - The enrolled role a manifest entry takes.
Functions§
- build_
resolver - Build the resolver from a manifest.
- foreign_
protocol_ keys - Every public key this node already holds for another protocol, as raw public-key bytes.