Chains & networks
Every testnet Botanary lists is available today; mainnets are recognized in the product and unlock over time.
Botanary operates across many chains, but not every chain offers the same capabilities, and not every mainnet it recognizes is turned on yet. Two things are true at once: which capabilities a chain offers is answered the same way everywhere, and which mainnets are actually usable right now can change as Botanary rolls them out.
Testnet now, mainnet as it unlocks
Every testnet Botanary supports is available today, with nothing to unlock. Mainnets are different:
Botanary's code recognizes a fixed list of mainnets, but a given mainnet only becomes usable once
Botanary deliberately turns it on. GET /chains is always the source of truth for what's actually
operable at a given moment - if a mainnet isn't in that response yet, it isn't live yet, regardless of
whether it's on the list below.
Chain capability tiers
Every chain your account can use is one of three tiers, and it's the same computation whichever way you ask - what a chain reports and what the backend itself enforces when building an operation can never disagree:
- Botanary tier - the account's on-chain rules engine (AgentGuard) is deployed, so freezing, delegating, and setting your own rules all work.
- Basic tier - no rules engine, but a bundler is available, so sending, swapping, trading, and the account-management actions under Manage all still work. Delegating is not available.
- Watch tier - read-only. Balances and activity, nothing else.
Trying an authority-level action - delegating, freezing, setting a rule - on a chain that doesn't
support it is refused outright as a build-time decline (chain_capability_unavailable), the same kind
of fail-closed behavior described in
Decline reasons. It's
never silently downgraded into something that looks like it worked.
Custom networks
You can add a network Botanary doesn't already list. A custom network is always Watch tier - its RPC calls run entirely on your device, and the backend never receives or proxies the RPC URL you supply. You also can't add a custom network using the same chain ID as a chain Botanary already operates on.
Supported chains
Testnets, available today:
| Chain | Chain ID |
|---|---|
| Robinhood Testnet | 46630 |
| Base Sepolia | 84532 |
| Arbitrum Sepolia | 421614 |
| Optimism Sepolia | 11155420 |
| Polygon Amoy | 80002 |
| Ethereum Sepolia | 11155111 |
Mainnets Botanary's code recognizes, unlocking over time:
| Chain | Chain ID |
|---|---|
| Ethereum | 1 |
| Optimism | 10 |
| Polygon | 137 |
| BNB Chain | 56 |
| Avalanche | 43114 |
| Gnosis | 100 |
| Linea | 59144 |
| Scroll | 534352 |
| Blast | 81457 |
| Mantle | 5000 |
| Celo | 42220 |
| Unichain | 130 |
| Mode | 34443 |
| Zora | 7777777 |
| World Chain | 480 |
| Sonic | 146 |
| Base | 8453 |
| Arbitrum | 42161 |
| Robinhood | 4663 |
Robinhood Chain (both its testnet and mainnet) is pinned first wherever chains are listed - it's the one chain treated as a default point of reference across the product.
What a chain listing includes
Alongside its name and chain ID, each chain in GET /chains reports its capability tier, whether it's
a testnet, its native asset's symbol, which assets can pay for gas on it, and links to its block
explorer - always a Blockscout instance in this version.