Abraxas Identity Layer

Universal Trust Infrastructure for Tokenized Assets and Digital Identity

Verify Once. Transact Everywhere. Abraxas is not a KYC provider. It is a trust and credential orchestration layer. licensed verifiers perform KYC; Abraxas standardizes, secures, and distributes cryptographic proof with user consent.

The problem

Every exchange, protocol, RWA platform, and lender performs KYC independently because each is legally responsible for it. They do not trust each other's verification, and there is no universal trust framework.

Complete verification once with an approved provider. Receive a signed W3C Verifiable Credential bound to your wallet. Abraxas records only proofs. never passports or selfies. When another protocol needs compliance, it asks Abraxas for a signed answer instead of making the user upload documents again.

What Abraxas is. and is not

Not this
  • Another KYC vendor
  • Storing passports on-chain
  • Replacing Veriff's legal liability
  • Proprietary identity format
This
  • Trust registry & credential orchestration
  • Trusted issuer registry (roadmap)
  • Revocation & compliance engine (roadmap)
  • W3C VC + did:sui open standards
  • One API instead of five KYC integrations

Core principles

  • Users own their identity credentials
  • No passports or driver's licenses stored on-chain
  • PII remains with approved identity providers (Veriff, manual review)
  • On-chain: hashes, issuer attestations, timestamps, expiration, revocation status only
  • Every credential is cryptographically signed (W3C VC · Ed25519)
  • Every credential is revocable
  • Every verification is portable across participating protocols
  • User consent required before any proof is shared

What Abraxas stores (never the passport)

credential_hashSHA-256 of the VC payload. tamper-evident reference
issuerLicensed verifier or Abraxas attestation key (did:web:…)
wallet_bindingSui address (zkLogin). primary holder anchor
expirationCredential and stamp TTL; 0 = no expiry until policy change
risk_scoreDynamic 0–1000 trust score (roadmap)
sanctions_statusAML / OFAC screening outcome from provider
verification_levelBASIC · STANDARD · ENHANCED · ELITE stamp set
revocation_statusActive · revoked · superseded

How integrators use AIL

When a protocol needs compliance, it asks Abraxas. the user does not upload documents again.

Is this wallet verified?
GET /api/sui/passport?owner=0x… · POST /api/credentials/verify
Is the credential still valid?
Check expiration + revocation + issuer signature
Is this user eligible for US investors?
Compliance engine. jurisdiction rules (roadmap)
Has AML screening passed?
Stamp bitmask + sanctions_status in credential subject
Which issuer performed KYC?
issuer field + trusted issuer registry (roadmap)
Can I trust this attestation?
Ed25519 verify against GET /api/credentials/public-key

System architecture

Layer 1. Identity providers
live

Licensed third parties perform verification. Abraxas does not replace their legal role.

  • Government ID + liveness (Veriff. live on /passport)
  • AML / sanctions screening (via Veriff outcome)
  • Business / property / asset manual review (Abraxas verifier queue)
  • Future: Persona, Sumsub, Trulioo, Parallel Markets (trusted issuer registry)

→ Signed W3C Verifiable Credential to user's wallet

Layer 2. Credential engine
live

Validates provider outcomes, issues Abraxas-signed JWTs, tracks lifecycle.

  • Validate signatures · create credential hashes
  • POST /api/credentials/issue · POST /api/credentials/verify (live)
  • Track expiration · revocation · credential identifiers
  • Encrypt off-chain metadata where required

→ did:sui credential + stamp bitmask reference

Layer 3. Trust registry
in progress

Who can issue, what was revoked, issuer reputation. the Stripe-of-trust registry.

  • Trusted issuer registry (roadmap)
  • Credential registry + revocation registry (partial. Supabase + on-chain revoke bit)
  • Issuer licensing metadata · supported jurisdictions (roadmap)
  • Institution reputation scores (roadmap)

→ Integrators trust one registry instead of five KYC vendors

Layer 4. Compliance engine
roadmap

Policy evaluation. PASS / FAIL / REVIEW for institution-specific rules.

  • Jurisdiction eligibility · accredited investor rules
  • Credential freshness (e.g. KYC within 12 months)
  • Sanctions re-screening · Travel Rule hooks
  • Institution-defined policy DSL

→ Signed compliance proof without exposing underlying PII

Layer 5. Identity wallet (Passport)
live

User-facing credential container. proofs only, no sensitive documents.

  • zkLogin sign-in → Sui holder address (live)
  • Sui Move Passport object. stamp bitmask (devnet live)
  • Multi-wallet binding + recovery (roadmap)
  • Cross-chain identifiers (roadmap. Sui primary today)

→ Abraxas Passport. reusable credentials for every participating protocol

Credential catalog (beyond KYC)

Identity
KYC · Biometric · Proof of address · Humanity verification
Business
KYB · Beneficial ownership · Institutional investor · Fund manager
Financial
Accredited investor · Income verification · AML cleared · Sanctions clear
Assets
Real estate ownership · Precious metals · IP / royalties · Mineral rights
Professional
Professional licenses · University degrees · Auditor · Appraiser · Custodian
Sovereign
Tribal credentials · Government agency attestation

Identity lifecycle

Initial verificationCredential renewalPeriodic AML / sanctions rescreeningWallet migration (multi-wallet binding)Credential expirationCredential revocationLost wallet recoveryAudit trail (consent + proof requests)

Role-based credentials

Different participants need different reusable credentials. each maps to Passport stamp bits.

IndividualBusiness (KYB)Institutional investorFund managerProperty ownerCustodianAuditorAppraiserTrusteeGovernment agency

Trust score (roadmap)

Dynamic 0–1000 score. not just initial KYC. Factors include:

  • Identity strength
  • Credential freshness
  • Verification history
  • Institutional attestations
  • Wallet age
  • Credential diversity
  • Sanctions history
  • Humanity verification

Developer API

Live today
  • POST /api/credentials/verify
  • POST /api/credentials/issue
  • GET /api/credentials/public-key
  • GET /api/sui/passport
  • POST /api/auth/zklogin/register
  • POST /api/idv/create-session
Roadmap
  • POST /verify · GET /proof · POST /consent · POST /revoke · POST /refresh
  • GET /trust-score · GET /credential/status · POST /wallet/link
  • GET /issuer · GET /supported-jurisdictions
  • Webhooks · policy engine · enterprise dashboard

Privacy by design

  • PII stays with identity provider whenever possible
  • Selective disclosure. reveal only what the request requires (zk roadmap)
  • On-chain: stamp bitmask + hashes. never document images
  • User consent before every proof share
  • Encrypted off-chain metadata where Abraxas must store references

Long-term vision

Build the core as a general-purpose trust engine. Ship reusable identity (KYC/KYB) as the first application. Expand to real estate, metals, IP, licenses, carbon credits, supply chain, and AI agent credentials - all on the same infrastructure.

  • Verification orchestration fees
  • Credential refresh & rescreening
  • Institution / enterprise subscriptions
  • Trust Score API
  • Compliance automation & white-label infrastructure
  • API usage · premium analytics

Related