Overview
Abraxas is reusable trust infrastructure for tokenized assets and permissioned finance. Users verify once; partners check cryptographic proof instead of re-collecting documents.
Documentation
Protocol docs
Each section fits one screen. Jump to a topic or follow Read more for depth.
Overview
Quick Start
Quick Start
Sign in with Google at /passport to create a Sui wallet automatically. Complete optional biometric ID verification. Partners call POST /api/credentials/verify with a presentation proof.
Core Concepts
Passport
Google zkLogin creates a deterministic Sui address. Identity verification is optional but unlocks enhanced trust for payments, asset submission, and partner policies.
Biometrics
Users submit legal name, government ID, and selfie. The biometric engine scores face match, liveness, document type, and fraud risk. Borderline cases queue for human review.
Trust Registry
Issued credentials can be presented to relying parties. Partners receive approve/deny/review decisions without receiving raw document images by default.
Assets
Assets move through staged verification: identity, ownership, legal, due diligence, risk scoring, and marketplace readiness. Each stage produces audit events.
Developer Docs
API
POST /api/credentials/verify · GET /api/credentials/public-key · POST /api/identity/documents/capture · GET /api/identity/status · POST /api/auth/zklogin/register
Architecture
AIL layers: providers, credentials, registry, compliance. Licensed or Abraxas-native identity capture → W3C Verifiable Credentials (did:sui, Ed25519 JWT) → trust registry and policy engine.
Security
Service role keys and signing keys are server-side only. Supabase RLS on all tables. Biometric assessments and reviewer actions produce audit records.
Roadmap
Roadmap
Live: zkLogin Passport, Abraxas Verify biometrics, credential issuance, admin review queue, Cielo pilot. In progress: mainnet deployment, expanded relying partners.