How Abraxas is built
Abraxas Identity Layer (AIL). five-layer trust infrastructure. Live vs roadmap labeled honestly.
Design principle
Abraxas is a trust orchestration layer, not a KYC vendor. Licensed providers perform verification; Abraxas stores only credential hashes, issuer, expiration, sanctions status, and wallet binding. External protocols integrate one API - Is this wallet verified?. instead of five different KYC stacks.
Read full AIL specification →Architecture stack
Portable verification on Sui. zkLogin for identity, personal-message intents for gas-free proofs, sponsored transactions for tier members updating Passport stamps.
- zkLogin sign-in on /passport (Google → Sui address)
- Intent messaging: sign challenge strings without a transaction (roadmap)
- Sponsored tx tiers: growth-fee treasury pays gas for stamp ops (roadmap)
- Signed presentation via POST /api/credentials/verify (live)
Licensed providers verify off-chain; Abraxas issues W3C credentials (did:sui) and records only hashes, issuer, expiration, sanctions status, wallet binding. Sui Move Passport anchors stamp bitmask on-chain.
- W3C Verifiable Credentials (did:sui:0x…)
- Ed25519 signed JWT issuance (POST /api/credentials/issue)
- Veriff Precheck on /passport (linked to zkLogin address)
- Sui Passport Move module. devnet live (GET /api/sui/passport)
- 10-stamp bitmask model
Stablecoin checkout for packages and bookings. A slice of verification growth fees funds the Sui sponsor treasury for tier-based gas sponsorship.
- Live: stablecoin transfer → treasury with Authorized → Captured → Settled
- Roadmap: x402 for verification packages
- Roadmap: automatic allocation to SUI_SPONSOR_TREASURY_ADDRESS
Wyoming LLC packages and verified assets (Cielo Sunrise) with Abraxas verification pipeline. Ownership credentials tied to Sui holder address.
- Wyoming LLC tiers on /build
- Cielo Sunrise genesis asset. live gallery + booking
- Asset submissions via V5 pipeline
Agents coordinate verification → review → stamp issuance → credential + on-chain mirror.
- Live: Human verifier queue for Business, Property, Asset Owner
- Roadmap: Auto issue_stamps on Sui after approval
Verify without re-KYC: JWT API today, on-chain bitmask read via Sui RPC tomorrow.
- Live: POST /api/credentials/verify
- Live: GET /api/sui/passport
- Live: GET /api/credentials/public-key
- Roadmap: Intent message verification SDK
x402 payment path (planned)
HTTP 402 for verification packages. programmatic settlement tied to credential + Passport stamp issuance.
- Client requests package → server responds 402 with price
- Payment completed (stablecoin or Sui)
- Portion allocated to sponsor treasury
- Review unlocked; credential + on-chain stamps issued
x402 sells verification as infrastructure. APIs and agents pay programmatically.
Passport root (Sui primary)
52-byte logical root. u16 stamp bitmask on Sui Move Passport object. zkLogin holder address. Full spec: /docs/passport-spec · hub: /docs/sui.
- verify(passport, required_stamps, timestamp) on Sui Move
- GET /api/sui/passport for off-chain integrators
- Type 0: Ed25519 over abraxas-passport-v1 || serialized root
- Type 1: zkLogin ZK presentation
- Intent: personal message sign (no gas)
No documents on-chain. only stamp bitmask and lifecycle fields.
Integrator quickstart
- Fetch issuer public key: GET /api/credentials/public-key
- Accept presentation JWT (did:sui) from user's Passport
- Verify: POST /api/credentials/verify
- Optional: GET /api/sui/passport?owner=0x… for on-chain stamps
- Learn features: /docs/sui
- POST /api/auth/zklogin/register
- GET /api/sui/passport
- POST /api/credentials/verify
- GET /api/credentials/public-key
- GET /api/passport/spec