DIONE Wallet Multi-Chain Support — EVM Chains Beyond Odyssey

Yes — Odyssey natively, plus other EVM chains via custom RPC. Here's exactly which chains work and which don't.

Last updated: 2026-05-03

---

What "EVM compatibility" means in practice

DIONE Wallet is an EVM (Ethereum Virtual Machine) wallet. Any blockchain that implements the EVM specification works with the same wallet software, the same address format (0x...), the same signing logic, and mostly the same RPC interface.

The chain-specific differences are:

1. Chain ID — a numeric identifier (Ethereum = 1, Polygon = 137, Odyssey = 153153, etc.)
2. RPC endpoint — the URL the wallet connects to to read chain state and submit transactions
3. Native token — what gas is paid in (ETH on Ethereum, MATIC on Polygon, DIONE on Odyssey)
4. Block explorer — where the wallet links you to view transactions

Adding a new EVM chain to DIONE Wallet is essentially configuring those four values. The wallet doesn't need a code update for each new chain — it just needs the configuration.

This is why "EVM-compatible" is meaningful: one wallet works with dozens of chains, with a small per-chain setup. It's also why DIONE Wallet can support Odyssey natively and others via custom RPC without a fundamentally different code path.

Adding Ethereum mainnet to DIONE Wallet

The most common multi-chain question. Here's how:

1. Open DIONE Wallet → Settings → Networks → Add network
2. Fill in:
   • Network name: Ethereum Mainnet
   • RPC URL: https://eth.llamarpc.com (or your preferred public RPC, or your own Alchemy/Infura key)
   • Chain ID: 1
   • Currency symbol: ETH
   • Block explorer: https://etherscan.io
3. Save

Now you can switch between Odyssey and Ethereum from the network dropdown. Your address is the same on both chains (same private key, same 0x... address), but the balances are independent — DIONE on Odyssey, ETH and ERC-20 tokens on Ethereum.

The same procedure works for any other EVM chain. The chain-specific values for the popular ones:

Chain	Chain ID	Public RPC	Native token
Ethereum	1	https://eth.llamarpc.com	ETH
Polygon	137	https://polygon-rpc.com	MATIC
Arbitrum One	42161	https://arb1.arbitrum.io/rpc	ETH
Optimism	10	https://mainnet.optimism.io	ETH
BNB Chain	56	https://bsc-dataseed.binance.org	BNB
Avalanche C-Chain	43114	https://api.avax.network/ext/bc/C/rpc	AVAX
Base	8453	https://mainnet.base.org	ETH

Use chainlist.org for the canonical, regularly updated list of chain IDs and RPC endpoints.

What works on each added chain

Once you add an EVM chain via custom RPC, DIONE Wallet's standard features mostly work:

Works fully:

• View native token balance
• View ERC-20 token balances (you may need to manually add the contract address for tokens not auto-detected)
• Send and receive transactions
• Connect to dApps via WalletConnect v2
• Sign messages
• Hardware wallet support (Ledger, Trezor, Tangem) — same hardware works for any EVM chain

Works but Odyssey-specific:

• Native staking UI — only for Odyssey. Other chains have their own staking dashboards (Lido for Ethereum, etc.) accessible via WalletConnect.
• Validator picker / OBOL leaderboard — Odyssey-specific
• Migration verifier — only verifies the original 2024 ERC-20 → Odyssey migration

Doesn't work without configuration:

• Token discovery on chains with thousands of tokens — you may need to import contract addresses manually for niche tokens
• NFT display — limited at v1.0.1; works for some standards on Ethereum but not optimized for multi-chain NFT views

If your primary use case is "manage NFTs across 5 chains," DIONE Wallet at v1.0.1 isn't the right tool. If your primary use case is "hold DIONE plus occasionally use ETH or stablecoins on a few chains," DIONE Wallet handles it fine.

Why DIONE Wallet doesn't auto-include all EVM chains

A reasonable question: if any EVM chain works via custom RPC, why does DIONE Wallet ship with only Odyssey native and require manual setup for others?

The honest answer is product positioning. DIONE Wallet is the canonical wallet for Odyssey Chain. Auto-including 50+ chains in the default UI dilutes that positioning and creates support burden — every chain you officially support, you implicitly endorse. If a public RPC for chain X gets compromised, users on chain X point fingers at the wallet for "approving" that RPC.

The custom-RPC path makes you the trust authority for the chain configuration. You picked the RPC, you take responsibility for it. This shifts trust appropriately and keeps the default wallet UX clean for the primary use case.

This may change over time. As DIONE Wallet matures, expect a curated "Add chain" gallery with vetted RPC defaults. At v1.0.1, the manual path is the only path.

Non-EVM chains

DIONE Wallet does not support non-EVM chains:

• Bitcoin — different cryptography (secp256k1 with different signing scheme), different transaction format, no smart contracts in the EVM sense. Use a Bitcoin-specific wallet (Sparrow, Electrum, hardware-wallet companion app).
• Solana — different VM (BPF), different address format. Use Phantom, Solflare, or hardware wallet companion.
• Cardano — different VM (Plutus). Use Lace, Yoroi, Daedalus.
• Cosmos chains (ATOM, OSMO, etc.) — different transaction model. Use Keplr or Cosmostation.
• TRON, XRP, Algorand, Tezos — each different. Each has its own wallet ecosystem.

If you hold significantly across non-EVM chains, you'll need separate wallets for each, or an aggregating wallet like Trust Wallet that handles them all (with the trade-off of breadth over depth).

Token detection on non-Odyssey chains

DIONE Wallet auto-detects DIONE balance on Odyssey because it knows the chain natively. On other added chains, token detection works for popular tokens but may miss niche ones.

If you hold a token that doesn't appear:

1. Find the token's contract address on the relevant block explorer (Etherscan, Polygonscan, etc.)
2. In DIONE Wallet, switch to that chain
3. Settings → Tokens → Add custom token
4. Paste the contract address
5. Decimals usually auto-fill from the contract; if not, look them up on the explorer

Common token contract addresses are well-documented on coingecko.com and the official websites of each project.

Security considerations across chains

A few things to watch when using DIONE Wallet across multiple chains:

Public RPC trust. When you add a public RPC like https://eth.llamarpc.com, you're trusting that RPC to give you accurate chain state and to broadcast your transactions. A compromised RPC could show you a fake balance or fail to broadcast transactions. For high-value operations, consider running your own node or paying for a dedicated provider (Alchemy, Infura, Ankr).

Cross-chain transaction confusion. With multiple chains added, it's easy to send a transaction on the wrong chain. Common mistake: trying to send DIONE while connected to Ethereum (it doesn't exist there as a token in any meaningful way). Always check the active network indicator before signing.

Approvals scope. DApps approve token spending per chain. Approving USDC spending on Polygon doesn't approve it on Ethereum. Each chain has its own approval state. Use revoke.cash to audit your approvals across chains periodically.

Attack surface. Each chain adds a new transaction-signing surface. Fake-airdrop signature requests are most common on chains with high token activity (Ethereum, Polygon, BNB Chain). Verify the contract address on the source chain before signing any unsolicited transaction prompt.

---