Add chain contracts

Build, resolve, link, and diagnose Base, Solana, and Algorand contract metadata for a Gora app.

Add chain contracts

A Gora app can be off-chain only, but many apps also need a chain contract, gateway, program, or smart wallet.

Use a chain contract when you need to:

• verify a Gora result or attestation on-chain
• hold app state
• execute transfers or callbacks
• enforce replay protection
• connect mobile/user signatures to chain execution

Key rule

gora deploy deploys your Gora app package.

It does not deploy Base contracts, Solana programs, or Algorand applications.

Use gora contract ... for chain contract metadata:

gora contract build --chain <chain>
gora contract deploy --chain <chain> --node https://gora-bridge.74.241.248.103.nip.io
gora contract link --chain <chain>

Then deploy the app package:

gora deploy

Local developer vs node operator

If you are developing from your local computer, prefer --node:

gora contract deploy --chain algorand --node https://gora-bridge.74.241.248.103.nip.io

This asks the Gora testnet node for already deployed chain metadata and records it locally. Live endpoints and deployed contract IDs are listed in Connect to the testnet.

If you are the node operator on the VM, you may deploy directly using local chain files and tools, such as Algorand --datadir.

Contract metadata endpoint

The Gora node exposes chain metadata at:

curl https://gora-bridge.74.241.248.103.nip.io/v1/contracts
curl https://gora-bridge.74.241.248.103.nip.io/v1/contracts/algorand
curl https://gora-bridge.74.241.248.103.nip.io/v1/contracts/base
curl https://gora-bridge.74.241.248.103.nip.io/v1/contracts/solana

Only Algorand contract flows are live on the public testnet today; the base and solana entries report their local-devnet status.

Example Algorand response (live testnet values — gateway app 767488273):

{
  "ok": true,
  "chain": "algorand",
  "contract": {
    "chain": "algorand",
    "kind": "algorand_application",
    "name": "GoraAlgorandGateway",
    "role": "app_contract",
    "status": "deployed",
    "app_id": "767488273",
    "address": "767488273",
    "deployment_tx": "TX_ID",
    "network": "testnet",
    "chain_id": "testnet-v1.0",
    "rpc_url": "https://testnet-api.algonode.cloud",
    "auth": {
      "type": "algod_token",
      "header": "X-Algo-API-Token",
      "token_env": "ALGORAND_ALGOD_TOKEN",
      "token_included": false
    }
  }
}

Algorand testnet algod is public and needs no token (token_included: false).

The CLI uses the same endpoint when you run gora contract deploy --node ....

Diagnose setup

Run doctor before deploying:

gora contract doctor --chain algorand --node https://gora-bridge.74.241.248.103.nip.io

Doctor checks local source/build/deploy receipts and remote contract metadata when a node URL is provided.

Base/EVM

Build metadata:

gora contract build --chain base

Resolve the gateway or contract address from a node:

gora contract deploy --chain base --node https://gora-bridge.74.241.248.103.nip.io

The separate Gora Base gateway is not deployed, so this metadata lookup returns needs_deployment. Base Sepolia staking and managed-agent app writes are live; deploy your own app contract and follow the Base/Solana quickstart.

Or record a known address manually (local-devnet values shown):

gora contract deploy \
  --chain base \
  --rpc https://YOUR-BASE-RPC-URL \
  --address 0x0000000000000000000000000000000000000000 \
  --deployment-tx 0xTX

Link it into the manifest:

gora contract link --chain base

Solana

Build metadata and default source scaffold:

gora contract build --chain solana

Resolve the program id from a node:

gora contract deploy --chain solana --node https://gora-bridge.74.241.248.103.nip.io

The separate Gora Solana gateway is not deployed, so this metadata lookup returns needs_deployment. Solana devnet staking and managed-agent app writes are live; deploy your own program and follow the Base/Solana quickstart.

Or record a known program id (local-devnet values shown):

gora contract deploy \
  --chain solana \
  --rpc https://YOUR-SOLANA-RPC-URL \
  --program-id Gora111111111111111111111111111111111111111 \
  --deployment-tx EXISTING_SIGNATURE

Link it:

gora contract link --chain solana

Algorand

Build gateway TEAL metadata:

gora contract build --chain algorand

Normal local developer flow:

gora contract deploy --chain algorand --node https://gora-bridge.74.241.248.103.nip.io
gora contract link --chain algorand

This records the deployed Algorand app_id from the node — on the public testnet that is gateway app 767488273 (see Connect to the testnet).

VM/operator direct deploy flow (local devnet only):

gora contract deploy \
  --chain algorand \
  --rpc https://YOUR-ALGORAND-RPC-URL \
  --datadir /path/to/algorand-localnet/Node

--datadir must point to a local Algorand Node/ directory containing algod.net and algod.token. It only works on the machine running that Algorand localnet.

Manual record-existing flow (live testnet values):

gora contract deploy \
  --chain algorand \
  --rpc https://testnet-api.algonode.cloud \
  --app-id 767488273 \
  --deployment-tx EXISTING_TX_ID

What linking writes

gora contract link --chain <chain> updates gora.app.json with a contract binding similar to:

{
  "chain": "algorand",
  "kind": "algorand_application",
  "name": "GoraAlgorandGateway",
  "address": "767488273",
  "deployment_tx": "TX_ID",
  "chain_id": "testnet-v1.0",
  "network": "testnet",
  "role": "app_contract"
}

After linking, run:

gora validate
gora deploy

Custom fulfillment contracts

For custom EVM contracts, prefer a gateway-mediated callback. The custom contract should accept calls only from the trusted Gora gateway and reject duplicate request ids.

Minimal interface:

interface IGoraFulfillmentReceiver {
    function fulfillGoraRequest(
        bytes32 requestIdHash,
        bytes32 appIdHash,
        bytes32 outputHash,
        bytes32 attestationHash,
        bytes calldata result,
        bytes calldata proof
    ) external;
}

Your contract should verify:

• caller is the trusted gateway
• request id was not already fulfilled
• app id matches your app
• output hash matches the supplied result
• proof/attestation was accepted by the gateway
• decoded result satisfies your policy limits

Next: Set policy and payments.