Chains and environments

The two chains#

Both the launchpad and the prediction markets deploy to Robinhood Chain. The subject of a market and the money staked on it are the same chain, so nothing here is bridged and nothing is attested — a market settles by calling a view on the bonding curve it is about.

The explorer URL, the RPC endpoints and the native currency for a chain are published as fields of that chain’s own addresses file — explorer, rpc[] and nativeCurrency. Read them from there rather than from this table: the file is generated at build from the deployment records, so it cannot be stale in a way this page would not be.

Environments#

Three environments, two chains. Dev and staging share chain 46630 and are separate deployments of the same contracts, distinguished by their deployment record rather than by their chain id.

Each origin serves the file for the chain it is configured against, and the file names which one it is: its environment field carries the calibration profile the deployment was made under. Two origins serving chain 46630 will serve two different files with two different sets of addresses, which is the point — a dev launch does not exist on staging.

A testnet figure is not a production figure#

The same caution applies to any absolute figure: fee rates, graduation targets and the graduation ladder are all settable on chain and are calibrated per environment. They are deliberately absent from the addresses file for that reason — a build-time copy of a settable value goes stale silently. Read them live from the contract that holds them.