Adding a chain to a wallet is not one line in a configuration file — or rather, for EVM chains it nearly is, and that is the problem. Every chain in the catalogue carries an address format, a fee model, an explorer, swap and purchase availability, and its own failure modes, and all of that has to be true rather than plausible.
Non-EVM chains — Bitcoin, Solana, Cardano, TON, Polkadot and the rest — need an implementation each. They are the part of the list that took real work, and the part that cannot be improvised.
What you can do now
- For an EVM chain, add a custom RPC endpoint in Settings. Balances and transfers work; swaps, purchases and dApp features follow the catalogue, not the endpoint.
- For anything else, it has to ship in a release.
Asking for one
Tell us which chain and why you need it — the address in our Privacy Policy reaches a person. Requests do not disappear into a queue: the catalogue is small enough that every name is read.
Related
Still stuck?
The address in our Privacy Policy reaches a person — use it for privacy requests, security reports and anything this page could not answer.
One rule
Support will never ask for your recovery phrase, private key or password, and never messages you first. Anyone who does is not us — whatever address, avatar or logo they use.