Deployment and parameters

Everything on this page is public information. None of it is a secret, and none of it needs configuring to use Elgora's own deployment — the clients ship with it built in.

The public deployment

Elgora runs on Base mainnet (chain id 8453) and escrows real USDC, which has 6 decimals. This is the default for the CLI and every client.

The testnet deployment

A second, separate deployment runs on Base Sepolia (chain id 84532) with test USDC, for trying Elgora without real money. Select it with --network base-sepolia or ELGORA_CHAIN_ID=84532; the CLI then resolves every value below on its own. Its bounties, Guardians, and data are separate from mainnet's, and its protocol configuration differs.

Configuration

The escrow token is read from ElgoraHub. The environment holds only secrets: ELGORA_PRIVATE_KEY, the local key of whichever role runs the command, and a Privy signer's PRIVY_APP_ID, PRIVY_APP_SECRET, and PRIVY_AUTHORIZATION_PRIVATE_KEY.

To target a deployment the client does not know, supply a complete, coherent set — chain id, Hub, RPC, subgraph, and API — and never mix values from different deployments.

Values that change

Everything in this group is mutable public state on the Hub, so nothing here, in a client, or in any configuration file records a copy of it — a stale fee or recipient is worse than no default at all. All of it is served by the subgraph: every value below is announced by an event, so this stays a pure projection, and the Hub stays authoritative regardless of where you read it. The app's status page shows the current values, read from the subgraph.

Served by the subgraph

Protocol is a singleton — one row for the whole deployment, keyed by the Hub address: protocol(id: "0x<hub_address>") returns one plain object, never a list. It exposes no change-history list; without a block, it returns the latest indexed value, including the live roster nested under guardianRoster. @elgora/subgraph-client wraps this further — client.getDeploymentConfig() reads it, plus the active-Guardian list, in one request once the client is constructed with hubAddress; pass an indexed block number to pin the read to that block.

The Bounty row is the one integrators most often want, and reads differently from the configuration rows: a bounty snapshots those values at creation, so they never move afterwards, and they are exactly what the projection carries. Reading Protocol's live fee rate instead tells you what a new bounty would get. Its guardianFeeClaimable field answers a different question again: the single global pool available at that indexed block.

# a contract read still works, and needs no subgraph indexing lag
cast call $ELGORA_HUB_ADDRESS "treasuryFeeBps()(uint16)"          --rpc-url $ELGORA_RPC_URL
cast call $ELGORA_HUB_ADDRESS "guardianFeeBps()(uint16)"          --rpc-url $ELGORA_RPC_URL
cast call $ELGORA_HUB_ADDRESS "minimumEscrowAmount()(uint256)"    --rpc-url $ELGORA_RPC_URL
cast call $ELGORA_HUB_ADDRESS "maximumEscrowAmount()(uint256)"    --rpc-url $ELGORA_RPC_URL
cast call $ELGORA_HUB_ADDRESS "minBountyDuration()(uint64)"       --rpc-url $ELGORA_RPC_URL
cast call $ELGORA_HUB_ADDRESS "maxBountyDuration()(uint64)"       --rpc-url $ELGORA_RPC_URL
cast call $ELGORA_HUB_ADDRESS "guardianReviewWindow()(uint64)"    --rpc-url $ELGORA_RPC_URL
cast call $ELGORA_HUB_ADDRESS "paused()(bool)"                    --rpc-url $ELGORA_RPC_URL

Publishing also quotes you the fee policy read at that moment, before you sign anything — see The readiness review.

Constants

Fixed at deployment, unchangeable by anyone:

Public surfaces

Verifying a deployment yourself

Every address above is checkable without asking anyone:

• the Hub's creation transaction and deploy block are listed here, so you can confirm the contract at that address was created by that transaction;
• source verification records are published for each contract, so you can compare the deployed bytecode with published source;
• the escrow token address is immutable at Hub construction — read ESCROW_TOKEN() from the Hub and confirm it matches;
• the Hub's live configuration is all public reads, as above.

Do not treat a hosted API or subgraph response as proof of what is deployed on chain. They serve whichever release was last promoted, and may lag the contracts.