Verifiable registry
Scope
The registry gives a verifier one resolution surface across the credential categories the framework spans. The per-jurisdiction Issuing Authority Certificate Authorities of the mobile driver’s license ecosystem, the ICAO Public Key Directory, and the eIDAS trust framework remain the authoritative sources for their own categories; the Foundation neither owns them nor proposes to. The registry holds three kinds of content under a verifiability contract: trust anchors, ratified schemas, and trust events. For each, the contract requires append-only history, verifiable inclusion proofs, integrity of governance events, and public auditability. It specifies the property, not the data structure. The registry stores no credential-holder data. Trust extension events are signed by Foundation governance keys; an extension without a valid governance signature is not honored, whoever operates the registry.
Operational properties
Each ratified specification carries commitments on privacy (the deployment holds no stable, deployment-specific identifier for the holder, because it issued nothing; schema-level disclosure constraints; decline-for-insufficient-disclosure as a defined outcome), revocation (issuer-side and access-side paths kept separate, the access-side path under a defined propagation contract), audit (federated chain, tenant data stays with the tenant), and offline operation (deterministic policy on cached trust data with bounded freshness; reconciliation on reconnect; egress and life-safety paths never depend on audit-buffer state). Sections 6.1 through 6.4 of the paper state them in full.
Public review
No review period is open.
Want to be notified when this specification opens for public review? Register on the Participate page.
Disposition log
No review periods recorded yet.
Text
Not yet published.
Related
Paper reference: Section 5.2 of Beyond Credentials (Beyond Credentials)
Adjacent standards: