Article II · Symmetry of Standards
The Standards Bridge
One signed fact, expressed in every language the internet already trusts. Nothing is re-signed and nothing is invented — each export is derived deterministically from the bytes the member signed.
Input
Paste a receipt
Output
Choose a format
The receipt as a credential issued by a did:key. Slots straight into wallet and trust-registry infrastructure.
Paste a receipt to see its equivalent in this format.
A translation cannot make a claim truer. If the original receipt is a lie, the Verifiable Credential is the same lie in a wallet-shaped envelope. All four formats prove exactly one thing: these bytes existed, signed by this key, at this time.
Coverage
What each format unlocks
RFC 8785 + Ed25519
Apex PSI receipt
The original signed artefact. Everything below is derived from it and adds nothing.
This nation, the offline verifier, any Ed25519 library
W3C VC Data Model 2.0 · Data Integrity eddsa-jcs-2022
Verifiable Credential
The receipt as a credential issued by a did:key. Slots straight into wallet and trust-registry infrastructure.
Digital identity wallets, EUDI wallet stacks, DIDComm agents
in-toto Attestation Framework v1
in-toto Statement
The receipt as a software-supply-chain attestation. CI systems can gate deploys on it today.
SLSA, Kyverno, Gatekeeper, GitHub attestations, policy engines
Dead Simple Signing Envelope
DSSE envelope
The transport envelope the signing ecosystem already ingests, with the Ed25519 signature intact.
Sigstore (cosign), Rekor, Tekton Chains
C2PA 2.x compatible manifest (sidecar, not embedded)
Content Credentials sidecar
The receipt expressed as a C2PA-shaped manifest so media tooling can read our provenance without new code.
Provenance viewers, newsroom pipelines, media asset managers