Skip to content
SBX IDSBX ID home

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.

Data sealed in vaultZKenginePlatformasks: accredited?proof: yes

$16T

Tokenized market by 2030 needing compliant identity

$30

Duplicate KYC cost per user, per platform

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

  • WeakTraditional KYCRe-verify on every platform
  • PartialSelf-sovereign IDDepends on adoption
  • StrongSBX IDOne credential, everywhere

Privacy of personal data

  • WeakTraditional KYCFull documents shared
  • PartialSelf-sovereign IDSelective disclosure
  • StrongSBX IDZK proofs, nothing revealed

Accepted by regulators

  • StrongTraditional KYCEstablished practice
  • WeakSelf-sovereign IDNot recognised
  • StrongSBX IDBuilt to regulator standards

On-chain enforcement

  • WeakTraditional KYCOff-chain only
  • PartialSelf-sovereign IDLimited
  • StrongSBX IDSoulbound token and ZK at transfer

One-time verification

  • WeakTraditional KYCRepeated per platform
  • PartialSelf-sovereign IDVaries
  • StrongSBX IDVerify once, reuse forever

DeFi native

  • WeakTraditional KYCNot built for it
  • PartialSelf-sovereign IDEmerging
  • StrongSBX IDPermissioned pools from day one