Why unified KYC is hard for RWAs — and how Abraxas solves it
Verification debt is the hidden tax on every permissioned on-chain transaction.
Why this problem has been hard
Each platform asks the same person for the same passport because it needs an auditable answer under its own risk rules — not because forms are hard to design.
Identity, liveness, sanctions, wallet control, accreditation, and asset title are separate claims with different issuers, assurance levels, and expiry.
Raw PII cannot live on-chain. The product is signed proof + selective disclosure — share the claim, not the document.
A verified person is not automatically tied to a wallet. Binding requires a signed challenge and step-up for high-value actions.
Verifiers configure their own rules and receive approve / deny / manual review with consent receipts and decision references.
Passports expire, sanctions lists change, wallet risk shifts. Verify once, refresh only what changed or expired.
How Abraxas solves it technically
Issuer: licensed ID provider, screening firm, or appraiser signs tamper-evident claims.
Holder: Abraxas Passport shows credentials, expiry, and exactly what each partner will receive.
Verifier: policy engine returns approved / denied / manual review with audit trail.
Partners receive only the claims their policy requires — never passport images, biometrics, or full profiles by default.
Decisions are time-bound. Re-check claim status before booking capture, investment, or token transfer.
Cielo booking, payment, and RWA transfer gates evaluate live claims — not a static dashboard badge.
Hybrid architecture
Verify once with approved providers, reuse eligible credentials across participating applications — share the proof, not the documents.
- Sui: zkLogin, W3C credentials, Move Passport, USDC settlement
- Solana: $ABRA optional access tiers — verification is not gated
- Credentials are portable by W3C standard — verify signature anywhere