Documentation

Protocol docs

Each section fits one screen. Jump to a topic or follow Read more for depth.

Overview

Overview

Abraxas is reusable trust infrastructure for tokenized assets and permissioned finance. Users verify once; partners check cryptographic proof instead of re-collecting documents.

Quick Start

Quick Start

Google zkLogin creates an account only. A partner policy requests only missing evidence, then your server verifies the signed receipt before granting access.

Core Concepts

Biometrics

Identity or liveness is not the default path. A partner policy may request identity evidence only when that policy truly requires it. Google sign-in is account access only.

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

Partner Flow redirect, POST /api/credentials/verify, verification requests, and public receipt verification.

Progressive proof quickstart →Policy packs →Integration Kit →Integration Studio →Starter kit generator →Solana integration →Trading venue adapter →Trading venue profiles →Wallet Standard binding →Payment authorization →Portable action contract →EVM partner adapter →Chain-verifiable attestations →Solana onchain eligibility gate →EVM onchain eligibility gate →Verified onchain gate deployments →Chain attestation signer lifecycle →EVM wallet-control binding →Receipt key lifecycle →Selective disclosure →Reclaim private attestations →Eligibility presentation protocol →Cross-chain protocol access →Testnet gate deployment kit →Onchain verifier conformance →Policy compatibility →Reusable eligibility →Partner Action Control Plane →Sandbox partner contract →Partner Event Delivery →Receipt lifecycle events →Circle Arc testnet settlement →Multi-chain Mainnet readiness →Production review control plane →Production credentials →Policy proposals →Policy release candidates →Verification issuer trust →Reclaim private attestations →Eligibility presentation protocol →Cross-chain protocol access →Testnet gate deployment kit →Onchain verifier conformance →Organization eligibility →Hosted Partner Flow handoff →Partner Flow →Partner Flow API (OpenAPI) →Protocol compatibility manifest (JSON API) →AI agents →Partner verification requests →

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 & integration status

Live on abraxasworld.xyz: Partner Flow APIs, OpenAPI contract, P1-2 validity/idempotency, P1-3 audit traceability. Open gates: IAT, external security review, v1.0.0-beta.0.