Wrong network
Switch to the correct chain before signing or sending funds.
What you are seeing#
A build of the venue settles on exactly one chain. If your wallet is connected to any other chain, a banner appears under the navigation, every money control is disabled, and the only enabled control is the one that switches or adds the network.
This is a hard fail on purpose. A signature produced on the wrong network is how a user loses money, so the interface refuses to produce one. The refusal reads: "Your wallet is on chain X and this venue settles on chain Y. … nothing is signed until the network matches."
Fixing it#
Press Switch network (or Add network, before you connect). The interface sends your wallet the standard add-chain request with these fields, so you should never have to type them:
| Build | Chain id | Name | RPC | Explorer |
|---|---|---|---|---|
| mainnet stages | 4663 | Robinhood Chain | https://rpc.mainnet.chain.robinhood.com | https://robinhoodchain.blockscout.com |
| testnet stage | 46630 | Robinhood Chain Testnet | https://rpc.testnet.chain.robinhood.com | https://explorer.testnet.chain.robinhood.com |
| local stage | 31337 | Local anvil | http://127.0.0.1:8545 | none — the request omits the field |
The sequence is switch, add if the wallet has never seen the chain, switch again, then verify: several wallets accept an add and stay where they were, and only the final check tells those apart from a real switch.
Messages you may see#
- "Your wallet has never seen this network. Approve the prompt that adds it, then try again." — the wallet answered with the standard unrecognised-chain code; approve the add prompt.
- "The wallet accepted the network request but is still reporting a different chain. Switch networks in the wallet itself and try again." — the verify step failed; change the network from inside the wallet.
- "A request is already waiting in your wallet." — open the wallet and answer the pending prompt before pressing anything again.
Local development#
On a local node, restarting the node resets the chain but not your wallet's cached nonce for chain 31337, and the next transaction fails with a generic internal error. The interface names this case on the local stage only, with the fix: clear the account's activity data in the wallet's advanced settings and send again. On a public network the same generic error means something else, and the interface does not give that advice there.