Chains control which blockchains the AI scans when a user connects their wallet. Enable only the chains your protocol is deployed on. The AI will scan those networks when looking up wallet history and querying contract state.
Supported chains
Ethereum Mainnet
The original EVM chain. Enable if your token or contracts are on ETH mainnet.
Base
Coinbase's L2. Enable for Base-native protocols and tokens.
BNB Chain
Binance's EVM chain. Enable for BSC-deployed contracts.
Polygon
High-throughput EVM sidechain. Enable if your contracts are on Polygon PoS.
Arbitrum One
Ethereum L2 rollup. Enable for Arbitrum-deployed protocols.
Optimism
Ethereum L2 rollup. Enable for OP-based protocols.
Avalanche C-Chain
Avalanche's EVM chain. Enable for Avalanche-deployed protocols.
Robinhood Chain
Read directly over RPC. Single transactions, revert decoding, native balance and gas all work; token balances and history need an indexer and are reported as unavailable rather than empty.
Monad
High-throughput EVM L1. The standard EVM engine applies: revert decoding, gas and approval checks, and failures that depended on state changing inside the block.
Aptos
Move-based L1. Reads on-chain modules and decodes Move aborts to diagnose failed transactions in plain English.
Sui
Move-based L1, read through public RPC with no key. Decodes Move aborts against published protocol error definitions, and explains the failures that are not aborts at all.
Hyperliquid
The perpetuals and spot exchange, not just the chain beside it. Reads a trader's orders and explains the exchange's own rejection reasons, which leave no transaction to look up.
Stellar
Read through Horizon and Soroban RPC. Explains path payments refused on price, missing trustlines, the minimum reserve, and Soroban contract failures.
Etherlink
The Tezos EVM Layer 2. Wallet and transaction lookups run through Blockscout rather than Moralis, which does not index it.
Sepolia (testnet)
Ethereum testnet. Enable during development to test wallet lookup without real assets.
Enabling and disabling chains
Toggle chains on or off from the Chains page. Changes save automatically after a short debounce. At least one mainnet chain must remain active at all times. The AI needs at least one chain to scan when responding to wallet questions.
Less is faster
Enable only the chains your users actually transact on. The AI scans all enabled chains on every wallet lookup; unnecessary chains add latency without adding value.
How chain detection works
When a user opens the widget and connects their wallet, the AI automatically queries their transaction history and relevant contract state across all enabled chains. The user doesn't need to specify which chain their question relates to. The AI infers context from what it finds on-chain and the content of the question.
Multi-chain protocols
If your protocol is deployed across several chains (for example, a bridged token on Ethereum, Arbitrum, and Base), enable all the relevant chains. The AI correlates activity across networks to give complete answers.