Developers · Solana devnet

Verify institutional access on Solana

Check a finalized Abraxas authorization and protocol-access transaction against the reviewed devnet bindings and current onchain accounts.

Transaction proof

Copy the signature from a successful access run after it reports broadcast: true. Do not enter an application ID, receipt ID, or API key.

How to get a signature

  1. Complete the institutional Partner Flow so Abraxas issues a current receipt.
  2. Run the local Solana devnet access proof with that receipt and your verified deployment ref.
  3. After the run reports broadcast: true, open the printed proof_url. It already contains the transaction signature.

Setting up a partner? Start in Launchpad. The application ID and deployment ref are setup values, not transaction signatures.

What this proves

A verified result means a successful finalized transaction contained the reviewed Ed25519 verification, gate authorization, and protocol-access activation instructions in order. The current authorization and entitlement accounts must match the signed attestation. Expiration is shown separately from historical execution. This check does not prove a broadcast replay attempt, production approval, or mainnet access.

No transaction signature yet? See the Solana gate documentation.