Abraxas Trust Framework
Separate issuers, assurance levels, and expiry. plus how trust stays current when records change.
Anyone pastes a proof ID. No account. No Abraxas login.
Trust is time-bound
Verify once means you do not re-upload documents to every counterparty. It does not mean “trust this forever regardless of what changed.”
Think of a signed certificate. like a notarized copy, but mathematical. It attests what was true at issuance. If something material changes, the certificate stops working until refreshed. Counterparties check validity at transaction time; they do not need to call Abraxas and take our word for it.
Verify once, reuse what remains valid, and refresh only what changed or expired.
Revoked or expired credentials must fail closed. always check state at transaction time, not cache indefinitely.
What triggers refresh. real estate & land
Recorded events. not random re-KYC. Sale, lien, and appraisal expiry are natural checkpoints.
- Credentials are cryptographic attestations. not Abraxas reputation scores
- Each claim has an issuer, assurance level, and expiry. not one eternal KYC checkmark
- Real estate fits because recorded events (sale, lien, title) are natural refresh triggers
- Decision receipts prove a policy outcome at a point in time; validity is recomputed when read
GET /api/verify/registry
KYC is not one checkmark
Each compliance question is an independent signed claim with its own issuer, assurance level, and expiry. A generic “KYC verified” badge must never imply all of these.
| Decision domain | Example claims | Who issues it | Status |
|---|---|---|---|
| Person & entity | Identity, liveness, KYB, UBO | Approved ID/KYB providers | Pilot / Partner-gated |
| Wallet & transaction | Wallet control, wallet risk, transfer permission | Abraxas + approved analytics/policy providers | Live / Planned |
| Investor eligibility | Accreditation, suitability, jurisdiction | Accredited verifier, issuer, broker-dealer | Partner-gated |
| Asset & collateral | Ownership review, title, appraisal, custody | Title firms, appraisers, custodians, attorneys | Pilot / Planned |
Claim reference
Operating model
Abraxas uses Sui zkLogin for low-friction account creation. Credentials remain chain-neutral and are presented as signed, time-bound claims. Wallet binding and transaction enforcement are chain-specific, beginning on Sui. Raw identity documents remain with approved verification providers; Abraxas stores only the minimum credential, consent, policy, and audit metadata required for the applicable workflow.