Versioned onchain verifier and conformance

Boundary

Allowed means the partner may perform its own named action. Abraxas never executes the trade, payment, membership grant, wallet connection, or protocol call. A presentation is one audience-bound, one-time eligibility result. It is not a transferable identity passport, not a reusable bearer credential, and not automatic KYC or KYB approval. The partner backend must re-fetch the current public receipt and apply its own policy. Abraxas shares a policy result, not the underlying evidence. This is enforced selective disclosure from the catalog, not a zero-knowledge proof system. A presentation is never sufficient. Re-fetch the current public receipt. No payable methods, token calls, arbitrary CPI, transfers, approvals, wallet creation, or custody.

Integration sequence

private eligibility
  → presentation + consent
  → public receipt re-fetch
  → chain attestation
  → partner-owned gate consume
  → local conformance report

1. Download verifier package
2. Run conformance locally
3. Fix any failed binding or stale signer
4. Request a fresh sandbox attestation

CLI

npm run abraxas-conformance -- evm <manifest>
npm run abraxas-conformance -- solana <manifest>
npm run abraxas-conformance -- vectors
npm run abraxas-conformance -- report <manifest>

EVM quickstart

Use schema 2, EIP-712 name AbraxasEligibilityVerifier, version 2, and the published typehash. Your gate consumes the nonce once. Local Foundry vectors must match the TypeScript digest.

Solana quickstart

Use prefix ABRAXAS_CHAIN_ELIGIBILITY_V2 and a 468-byte message. Institutional configs reject 372-byte V1. Local ProgramTest vectors must match the TypeScript canonical bytes.

V1 vs V2 institutional compatibility

V1 372-byte / EIP-712 v1: allowed only on existing non-institutional deployments. V2 468-byte / EIP-712 v2: required when institutional_required is true. V1 against an institutional GateConfig: rejected. V2 never silently parses as V1.

What Abraxas verifies

• Exact chain-attestation schema version
• EIP-712 domain or Solana canonical prefix and length
• Trusted signer key ID and public verifier
• Partner, policy, action, environment, and deployment bindings
• V2 institutional commitments when required
• Expiry and one-time nonce / replay
• Current public receipt re-fetch

What your protocol still owns

• Deploying and operating the partner-owned gate
• Named action after a verified consume
• Human-operated testnet deployment and registration
• Policy review and production readiness

Related

Verified deployments · Testnet kit · Signer lifecycle · Presentation