Supported chains
Supported chains are the blockchain networks available in the Aragon platform. Each account belongs to one chain; account creation selects that deployment network before its metadata and governance are configured.
Mainnets host production accounts. Testnets support trial accounts.
| Chain | Chain ID | Network type | Account creation | Action simulation | Explorer |
|---|---|---|---|---|---|
| Arbitrum | 42161 | Mainnet | Available | Available | Arbiscan |
| Avalanche | 43114 | Mainnet | Available | Available | SnowTrace |
| BNB Smart Chain | 56 | Mainnet | Available | Available | BscScan |
| Base | 8453 | Mainnet | Available | Available | Basescan |
| Chiliz | 88888 | Mainnet | Available | Unavailable | Chiliz Explorer |
| Citrea | 4114 | Mainnet | Available | Unavailable | Citrea Explorer |
| Ethereum | 1 | Mainnet | Available | Available | Etherscan |
| Hemi | 43111 | Mainnet | Available | Unavailable | blockscout |
| Katana | 747474 | Mainnet | Available | Available | katana explorer |
| Monad | 143 | Mainnet | Available | Available | Monadscan |
| Optimism | 10 | Mainnet | Available | Available | Optimism Explorer |
| Polygon | 137 | Mainnet | Available | Available | PolygonScan |
| Robinhood Chain | 4663 | Mainnet | Available | Available | Blockscout |
| zkSync | 324 | Mainnet | Available | Available | ZKsync Explorer |
| BNB Smart Chain Testnet | 97 | Testnet | Available | Available | BscScan |
| Base Sepolia | 84532 | Testnet | Available | Available | Basescan |
| Ethereum Hoodi | 560048 | Testnet | Available | Available | Etherscan |
| Ethereum Sepolia | 11155111 | Testnet | Available | Available | Etherscan |
| Polygon Amoy | 80002 | Testnet | Available | Available | PolygonScan |
Account creation and action simulation have separate availability. Simulation uses Tenderly and requires the app's simulation support for the selected chain.
Explore shows mainnet accounts in All accounts and includes testnet accounts in Member when the connected wallet has a qualifying membership. Cross-chain execution requires a compatible controller and a configured route for the account's deployment; the destination picker follows those routes.
Last updated on