Developers · Onchain

Verified onchain gate deployments

You deploy and own the gate. Abraxas verifies that exact configuration, then issues chain-verifiable eligibility attestations bound only to the approved deployment ref.

What this is not

Abraxas does not deploy, upgrade, call, fund, or broadcast to your contract or program. Browser values are untrusted. RPC URLs, keys, receipts, claims, and transaction payloads are never stored or returned.

EVM registration

  1. Deploy AbraxasPartnerEligibilityGate yourself (local Anvil or your operator RPC — never through Abraxas).
  2. Compute runtime bytecode hash and the public config digest (chain id, gate address, partner/policy/action/environment/signer/subject hashes).
  3. Submit the exact EVM manifest from Partner Launchpad while signed in. Fields: schema_version, gate_type, network_id, chain_id, gate_address, bytecode_hash, config_digest, partner_hash, policy_hash, action_hash, action_type, action_scope, environment, signer_key_id, subject_binding_mode.
  4. The server checks tenant/app ownership, pinned policy/version/action, approved network posture, and supported gate type.
  5. A server-only RPC adapter reads code hash and config digest. No adapter means deployment_verification_unavailable. Unverified manifests are never accepted.
  6. Chain attestation issuance must send the opaque deployment_ref. EIP-712 verifyingContract comes only from the verified record.

Solana registration

  1. Deploy your copy of the eligibility gate program yourself. Abraxas does not deploy it.
  2. Submit program ID, GateConfig PDA, program digest, and config digest with the Solana manifest. Fields: schema_version, gate_type, network_id, program_id, partner_program_id, gate_config_pda, program_digest, config_digest, partner_hash, policy_hash, action_hash, action_type, action_scope, environment, signer_key_id, subject_binding_mode.
  3. A server-only RPC adapter checks program ID, PDA, and digest. Local ProgramTest fixtures are for tests only.
  4. Issuance binds the Solana program/config from the verified deployment ref, never from a partner request field.

Lifecycle and issuance

Submitted → verified sandbox → needs correction → production review required → revoked. Only verified sandbox deployments receive sandbox chain attestations. Only a separately reviewed production deployment receives production chain attestations. Changed code hash, config digest, network, partner, policy, action, signer key, or a revoked row blocks issuance. Institutional class is server-derived from the verified observation and the server-owned policy. Client require_institutional is ignored. Launchpad shows either “Requires institutional V2 attestations” or “Standard eligibility gate.”

Launchpad safe states: no_deployment_registered, awaiting_verification, verified_sandbox, production_review_required, signer_update_required, unavailable.

Network posture

evm_sandbox (31337) and solana_devnet follow the network registry. evm_mainnet and solana_mainnet stay on Production review. arc_circle_testnet may be registered only after an approved network configuration and a server RPC adapter exist. arc_circle_mainnet remains disabled. This path does not add Circle wallet, USDC, settlement, or execution.

Related

EVM gate · Solana gate · Chain attestations · Signer lifecycle · Testnet deployment kit · Partner Launchpad