Verify it yourself.
Don't take our word for it.
DCS Verify issues, verifies, and manages credentials as Ed25519-signed receipts — independently checkable without trusting the issuing vendor. Open standard. MIT-licensed. No vapor.
Three jobs, done cryptographically.
Issue a credential, let anyone verify it, manage its status over time — each step provable, none requiring trust in DCS.
Issue
Sign any document or credential with the issuer's Ed25519 key. A content ID is computed over the canonical unsigned form (RFC 8785 + SHA-256), returned as a portable receipt — optionally anchored on Base.
Verify
Anyone confirms signature, anchor, and live status from the receipt alone. Five honest states: valid, expired, suspended, revoked, renewed. No DCS account. No vendor trust required.
Manage status
Revoke, suspend, reactivate, or renew. Status lives in a privacy-preserving Bitstring list anyone can read — revocation is permanent, suspension reversible. Honest about state, always.
Hash-chained
Each receipt links to its predecessor by content hash. Insertion, deletion, reordering, or replacement all break the chain — tampering is immediately detectable, by anyone.
Wallet ready
Present credentials to, and verify presentations from, Google / Apple / EU wallets via OID4VP — with issuance into wallets over OID4VCI. Interoperable, not a silo.
Verify Badge
A one-line embeddable "Verified by DCS" badge for any site. Live status, links to the public verify page — the trust mark that travels with the credential.
You never have to trust us.
Every receipt carries its own proof. The verify page shows the raw materials so a skeptic can re-check independently.
Recompute the ID
Canonicalize the unsigned credential (RFC 8785 JCS), hash it (SHA-256). It must equal the receipt's CID.
Check the signature
Verify the Ed25519 signature against the issuer's public key — published on an identity layer (DCS uses a soul-bound token on Base mainnet).
Read the status
Look up the bit in the public Bitstring status list, confirm the anchor on Basescan. All without contacting DCS.
Compatible, not captive: an R+2 receipt MAY be embedded inside a W3C Verifiable Credential (eddsa-jcs-2022) where a deployment prefers VC transport — but the receipt itself is the lighter, high-volume primitive.
One line. Verified everywhere.
Drop the badge on any site. It renders live status and links to independent verification — like an SSL padlock for credentials.
<script src="https://verify.dcslabs.ai/badge.js" data-cid="sha256:…"></script>
Verification in your pocket.
DCS Verify is a PWA — point your camera at any credential QR and watch the proof check itself. What you see below is the live interface, not screenshots.
Scan
Point the camera at a credential QR — or paste the CID. Works on any phone, installs from the browser, no app store.
Check — independently
The app recomputes the hash, verifies the Ed25519 signature, checks the on-chain Base anchor and the public status list. Four proofs, none of them "trust us."
Verdict + raw materials
Valid, revoked, or unknown — with the raw materials one tap away so a skeptic can re-verify with their own tools.
Valid
Issue your first credential.
The R+2 standard is live and source-verified on Base. Verification is free and public. Start issuing in minutes — or verify something right now.