Institutional diligence
Private eligibility, with the evidence visible
Inspect the sandbox flow, the verifier code, and the remaining deployment gates. A code artifact or Vercel build does not imply a live chain integration.
Good Trouble
Sandbox example
Partner Flow eligibility result for a 21+ retail request. Partner owns any checkout.
Next proof: An independent partner production integration and measured usage.
Inspect evidence →Institutional eligibility
Sandbox example
sandbox_institutional_protocol_access v1: Technical sandbox policy only. It is not live KYB, KYC, AML/KYT, legal certification, production access, Utila integration, or permission to move funds.
Next proof: A reviewed live issuer, external partner validation, and Production policy approval.
Inspect evidence →Solana partner-owned gate
Code ready · not deployed
Reviewed V2 verifier artifact and local ProgramTest. No public devnet program ID or registered deployment is claimed.
Next proof: Human devnet deployment, independent observation, and verified sandbox registration.
Inspect evidence →EVM partner-owned gate
Code ready · not deployed
Sepolia deployment kit and local contract tests. No live partner contract or transaction is claimed.
Next proof: Partner testnet deployment, exact code/config verification, then registration.
Inspect evidence →Cielo Sunrise registry record
Planned
Reference asset dossier. Not a bookable stay or USDC payment.
Next proof: Independently verifiable booking and payment evidence before any live claim.
Inspect evidence →Boundary for a protocol partner
Abraxas returns a narrow, audience-bound eligibility result after holder consent. The partner verifies the current public receipt and owns wallet governance, AML/KYT, transactions, and execution. The sandbox institutional result is not live KYB or a Utila integration.
Read the presentation protocol →