Why SBX ID
Trusted, private and DeFi-ready. At once.
Every existing approach forces a trade-off: accepted but siloed, private but unrecognised, or open but non-compliant. SBX ID is built so you never have to choose.
Portable by design
Verify once and the credential travels with the user's wallet to every integrated platform. No re-submitting documents, ever.
Private by proof
Zero-knowledge proofs answer eligibility questions without revealing the data behind them. Documents stay encrypted off-chain.
Regulator-grade
Built to FATF, MiCA, VARA and MAS standards, with reliance provisions that keep platforms compliant, not exposed.
DeFi native
The credential is an on-chain token any contract can read, so permissioned pools work from day one, not as an afterthought.
Answer the question. Reveal nothing.
A platform asks whether a holder qualifies. The ZK engine answers from data that stays sealed in the vault and returns only a proof. The documents never move.
- Date of birth
- ••••••••
- Account balance
- ••••••••
- Education record
- ••••••••
- Net worth
- ••••••••
- Residence
- ••••••••
- Full legal name
- ••••••••
Documents are encrypted on your device and never leave the vault. Not even SBX ID can read them.
What the platform may ask
$16T
Tokenized market by 2030 needing compliant identity
$30
Duplicate KYC cost per user, per platform
1×
Verifications a user needs with SBX ID
How SBX ID compares.
Set side by side with traditional KYC and self-sovereign identity, the difference is not a feature. It is being all three things: accepted, private and enforceable, in one design.
Portable across platforms
- Traditional KYCRe-verify on every platform
- Self-sovereign IDDepends on adoption
- SBX IDOne credential, everywhere
Privacy of personal data
- Traditional KYCFull documents shared
- Self-sovereign IDSelective disclosure
- SBX IDZK proofs, nothing revealed
Accepted by regulators
- Traditional KYCEstablished practice
- Self-sovereign IDNot recognised
- SBX IDBuilt to regulator standards
On-chain enforcement
- Traditional KYCOff-chain only
- Self-sovereign IDLimited
- SBX IDSoulbound token and ZK at transfer
One-time verification
- Traditional KYCRepeated per platform
- Self-sovereign IDVaries
- SBX IDVerify once, reuse forever
DeFi native
- Traditional KYCNot built for it
- Self-sovereign IDEmerging
- SBX IDPermissioned pools from day one
| Criteria | Traditional KYC | Self-sovereign ID | SBX ID |
|---|---|---|---|
| Portable across platforms | Re-verify on every platform | Depends on adoption | One credential, everywhere |
| Privacy of personal data | Full documents shared | Selective disclosure | ZK proofs, nothing revealed |
| Accepted by regulators | Established practice | Not recognised | Built to regulator standards |
| On-chain enforcement | Off-chain only | Limited | Soulbound token and ZK at transfer |
| One-time verification | Repeated per platform | Varies | Verify once, reuse forever |
| DeFi native | Not built for it | Emerging | Permissioned pools from day one |