Deployments
The chain table and launch configuration below, Contract Addresses, Asset Registry and Pool Composition are all generated from the per-chain deploy manifests and deployment records, and regenerated on every deploy.
1. Testnet policy
Every chain is a row, keyed by chainId. Adding a chain adds a manifest, its records and a registry row; no page is edited.
Planned = deployment target awaiting launch, no contracts. Row backing is the chain registry plus that chain’s launch manifest (GET /v1/chains serves the registered ids); a chain absent from both has no reservation and no row here, whatever the SDK’s broader wallet-metadata list carries. A planned chain gets addresses in Contract Addresses at deploy time; until then, point integrations at a live chain.
Native gas differs per chain. The native currency of a chain is its manifest’s chain.nativeSymbol, shown in the table below and the per-chain section of Contract Addresses. Where the gas token is also a listed pool asset, a “max” send has to leave the fee behind, and the app reserves a gas buffer on that input.
The app reads the published per-chain deployment artifacts for whichever chain is selected. On testnet chains the pool assets are mocks, minted through the on-app faucet (TestnetFaucet) under daily caps: Asset Registry.
Marks for every listed asset arrive via the signed keeper push pipeline; provenance and on-chain verification in Mark Relayer.
Which addresses can change, and under what delay: Contract Addresses §Upgradeability.
| Chain | chainId | Status | Native gas | Pools |
|---|---|---|---|---|
| Monad | 143 | Live mainnet | MON | 1 of 1 created |
| Arc Testnet | 5042002 | Live public testnet | USDC | 2 of 4 created |
| BNB Chain | 56 | Planned | BNB | 1 defined |
2. Launch configuration
Per chain, from its deploy manifest: the configuration the launch ceremony applies, not a live read. Risk parameters can be moved after launch, so read live values on-chain (Admin, per pool). Leg status comes from the chain’s pool records: a leg with an LP receipt is deployed, a leg in a created pool without one is standby, and a chain with no records is planned. A core marked not created is defined but has no pool yet.
Launch configuration: Monad
| Setting | Core |
|---|---|
| Status | created |
| Base | USDC |
| Legs | 6 |
| Standby (listed halted, unseeded; no LP receipt) | no leg |
| Deployed (LP receipt recorded) | every leg |
Deposit-gated (DEPOSIT_GATED_BIT) | every leg |
| Swaps | allowlist only (SWAP_GATED_BIT) |
Coop arbitrage (COOP_ENABLED_BIT) | on |
maxLiabWeightBps | 10000 (off) |
depositCapCode | 22: 1,000,000 base tokens per leg |
| Flash | off |
Timelocks PROD_DELAYS (Access Control §3). Addresses: Contract Addresses. Assets: Asset Registry. Pools: Pool Composition.
Launch configuration: Arc Testnet
| Setting | Stable | Forex | Crypto | Equity |
|---|---|---|---|---|
| Status | created | not created | created | not created |
| Base | USDCB | USDCB | USDCB | USDCB |
| Legs | 5 | 6 | 9 | 11 |
| Standby (listed halted, unseeded; no LP receipt) | no leg | no leg | no leg | no leg |
| Deployed (LP receipt recorded) | every leg | no leg | every leg | no leg |
Deposit-gated (DEPOSIT_GATED_BIT) | no leg | no leg | no leg | no leg |
| Swaps | public | public | public | public |
Coop arbitrage (COOP_ENABLED_BIT) | off | off | off | off |
maxLiabWeightBps | 0 (off) | 0 (off) | 0 (off) | 0 (off) |
depositCapCode | 8003: 500,000 base tokens per leg | 8003: 500,000 base tokens per leg | 8003: 500,000 base tokens per leg | 8003: 500,000 base tokens per leg |
| Flash | off | off | off | off |
Timelocks TESTNET_DELAYS (Access Control §3). Addresses: Contract Addresses. Assets: Asset Registry. Pools: Pool Composition.
Launch configuration: BNB Chain
| Setting | Core |
|---|---|
| Status | planned |
| Base | USDC |
| Legs | 9 |
| Standby at launch (listed halted, unseeded) | 5 of 9 legs |
Deposit-gated (DEPOSIT_GATED_BIT) | every leg |
| Swaps | off (SWAP_ENABLED_BIT clear) |
Coop arbitrage (COOP_ENABLED_BIT) | off |
maxLiabWeightBps | 10000 (off) |
depositCapCode | 22: 1,000,000 base tokens per leg |
| Flash | off |
Timelocks PROD_DELAYS (Access Control §3). Addresses: Contract Addresses. Assets: Asset Registry. Pools: Pool Composition.
3. Pages
| Page | Content |
|---|---|
| 2.1. Contract Addresses | Addresses, roles, timelocks and signers, one section per chain |
| 2.2. Asset Registry | Assets per chain: address, decimals, feed |
| 2.3. Pool Composition | Cores per chain, their legs and parameters |