Supported Chains
The EVM chains Zyper AIO ships with, and how to manage them.
This page covers the EVM chain registry used by Tasks, RPC, NFTs, PnL entry points, and EVM Manage Funds.
EVM Registry
Zyper AIO ships with 18 EVM chains: 17 mainnets plus Sepolia.
| Chain | Chain ID | Native |
|---|---|---|
| Ethereum | 1 | ETH |
| Arbitrum | 42161 | ETH |
| Optimism | 10 | ETH |
| Base | 8453 | ETH |
| Polygon | 137 | POL |
| BSC | 56 | BNB |
| Avalanche | 43114 | AVAX |
| Linea | 59144 | ETH |
| opBNB | 204 | BNB |
| Ink | 57073 | ETH |
| Shape | 360 | ETH |
| Apechain | 33139 | APE |
| Abstract | 2741 | ETH |
| HyperEVM | 999 | HYPE |
| MegaETH | 4326 | ETH |
| Monad | 143 | MON |
| Bittensor | 964 | TAO |
| Sepolia | 11155111 | ETH |
Each chain entry includes display name, EIP-155 chain ID, native symbol, public RPC fallbacks, explorer URL, and optional default Disperse contract.
RPC Fallbacks
Every chain has at least one built-in public RPC fallback. Custom RPCs you add on the RPC page take priority. Public fallbacks are best effort and should not be treated as the fast path for contested mints.
Disperse Contracts
Most EVM chains use the same default Disperse contract. Bittensor intentionally has no default Disperse contract in the registry.
Visibility
Settings -> Chains visibility controls which EVM chains appear in pickers. Hiding a chain does not delete its registry entry or stored RPCs.
Some newer or testnet chains are hidden by default on fresh installs to keep pickers shorter. Enable them when needed.
Non-EVM Assets
Solana and Bitcoin wallets/funds use separate stores and tools. They are not part of this EVM chain table and do not use EIP-155 chain IDs.