Sandbox · Sandbox example
Good Trouble
Prove 21+ eligibility. The partner sees only the result. Evidence stays private.
Good Trouble trusts an existing Abraxas credential instead of asking users to verify again.
Try the sandbox example →
PRIVATE ELIGIBILITY PROTOCOL
Prove only what a service needs.
Abraxas is a private eligibility protocol. Your evidence stays private. Partners verify a current result on their server.
Prove eligibility, verify a result, or try a sandbox example.
PersonPartnerProtocol explorer
Use one private verification again with fresh consent. Abraxas does not execute trades, payments, or transfers.
SANDBOX EXAMPLE
See Abraxas in action
Prove you are 21+ for a cannabis retail request. The partner receives only an eligibility result. Your ID, date of birth, and documents stay private. This is a sandbox Partner Flow, not a live dispensary checkout.
- You prove 21+ eligibility
- The partner receives only the result
- Your evidence stays private
Good Trouble is a sandbox Partner Flow example. Abraxas never completes checkout or moves funds.
What you can do here
A capability map for people, partners, and protocol explorers. Every card opens a real Abraxas surface.
For people
Prove eligibility once and reuse it with consent.
For partners
Request a current result and verify it on your server.
- AvailablePartner FlowHosted request, consent, and server-side receipt verification.
- AvailableIntegration StudioGuided packs, snippets, and starter-kit generation.
- SandboxPartner LaunchpadSandbox workspace and readiness path for partner apps.
- AvailableDeveloper docsPartner Flow, adapters, and operator-safe protocol guides.
Protocol capabilities
Policy, adapters, and readiness. Not a trading or payments app.
- AvailablePolicy packsPinned policies that ask only for the outcome a partner needs.
- SandboxTrading accessEligibility preflight for venue access. Abraxas never places a trade.
- SandboxPayment authorizationCheckout eligibility preflight. Abraxas never moves funds or processes USDC.
- PlannedMulti-chain readinessAccurate sandbox, testnet, and Mainnet posture. No silent activation.
How Abraxas works
Holder → private policy result → fresh consent → partner-bound receipt → server-verified protocol action. Abraxas does not execute the partner action.
A person opens Passport and prepares only the eligibility a partner asked for.
Open Passport →The partner sees a current policy outcome. Evidence stays with the holder.
Selective disclosure →Reuse is allowed only when the holder consents again for that request.
Reusable eligibility →The partner receives a receipt bound to their request, not a reusable public secret.
Verify a result →The partner backend decides what to do next. Abraxas does not execute the action.
Partner action contract →
Where private eligibility is used
These are Abraxas capabilities, not implied partnerships. Availability is labeled from the protocol registry.
- SandboxPrivate membership and accessProve member eligibility without handing over documents.
- Sandbox preflightTrading venue accessPartner-preflight eligibility for market access. Abraxas never places an order.
- Sandbox preflight · no USDC movementPayment and commerce authorizationAuthorize a checkout decision from a current result. Abraxas does not process USDC or complete bookings.
- Sandbox · Mainnet plannedProtocol and token-gated accessEligibility for named protocol, member, or redemption access. The partner keeps execution.
- AvailableReusable verification across partner requestsUse one private verification again with fresh consent for compatible requests.
What the product proves
Policy result
Approved or denied for the requested policy. Nothing extra.
Minimal disclosure
Partners receive the result, not documents, wallets, or a profile.
Reusable receipt
A signed receipt can be verified again without repeating capture.
Partner verification
The server fetches the public receipt and grants the action.
Integrations
Partner Flow, Passport, Solana, Good Trouble, and Circle testnet.
How it works
- 1Holder completes required steps
Wallet sign-in and identity steps when the partner policy requires them.
- 2Policy evaluates eligibility
Abraxas returns approved, denied, or manual_review for the requested policy.
- 3Partner verifies the signed result
Example outcome field: "meets age requirement: yes", verified server side via the Partner Flow receipt contract.
Abraxas in three proofs
Protocol in action
Working flows first. Registry records and case studies are labeled so they are not mistaken for live bookings or payments.
Planned · Registry record
Cielo Sunrise
Genesis registry record. Not a live booking or payment rail.
A genesis asset dossier. Not a bookable stay and not a USDC payment.
View registry record →
Planned · Case study
Chickasaw Project
Property verification narrative for conventional diligence. Not a live deal.
Diligence narrative for conventional property verification. Not a live transaction.
Read case study →
Abraxas Passport
Reusable eligibility, not a public identity file
Open Passport to prove only the result a service needs.
A sandbox example you can try
Good Trouble is a labeled sandbox Partner Flow. It is not a live checkout, booking, or payment.
Sandbox example
Good Trouble
Prove 21+ eligibility. The partner receives only the result. Evidence stays private.
Try the sandbox example →Who Abraxas is for
For people
Less repetition. Less unnecessary data sharing. More control.
For businesses
Request policy specific proof without collecting more personal information than necessary.
Trust and next steps
Google sign-in opens an account. Eligibility is a result defined by each partner policy. Identity or liveness appears only when a policy truly requires it.
Ready to verify once?