What's inside a Solidus credential.
A credential is a small signed JSON document. Here's every field, what it does, and why it's signed by a validator instead of a single company.
Every field, explained.
Click a key in the JSON below to see what it does, who signed it, and what you can prove with it.
proofobjectThe BBS+ signature itself.
The cryptographic proof is what makes a Verifiable Credential verifiable. The credential issued on chain carries an Ed25519Signature2020 proof binding the issuer's DID, the credentialSubject contents and validFrom, which any verifier can check against the issuer's on-chain public key. Selective disclosure is a separate step: BBS+ over BLS12-381 lets a holder prove a subset of the claims without revealing the rest. That BBS+ implementation is unaudited; no external review of it has been performed.
Why a network signs your credential, not a company.
Traditional KYC: one company vouches for you. If they go offline or change their mind, your verification is gone. Solidus: a network of validators co-signs the issuance. No single party can revoke.
How this is different from a Sumsub-issued check.
| Property | Sumsub credential | Solidus credential |
|---|---|---|
| Format | Proprietary JSON | W3C Verifiable Credential |
| Portable across services | No | Yes (any Solidus-integrated service) |
| Selective disclosure | No | Yes (BBS+) |
| Issuer-independent verification | No (must call Sumsub API) | Yes (validators co-sign; verify locally) |
| Revocable by issuer | Yes (silently) | Yes (with on-chain revocation record) |
| Survives issuer shutdown | No | Yes |
| User controls disclosure | No | Yes |
| Standards-compliant | Proprietary | W3C VC 2.0 + DID Core 1.0 |
See it in your wallet.
Run a test verification, get a real credential issued to the demo wallet, inspect every field.