Add Odyssey Chain to MetaMask — Custom RPC Setup (Step-by-Step)

A practical RPC setup guide for users who want to keep MetaMask, with an honest comparison.

Last updated: 2026-05-01

---

Step 1 — Open MetaMask network settings

Open MetaMask. Click the network dropdown at the top (usually showing "Ethereum Mainnet" or whichever network you last used).

If you don't see a custom networks option immediately, click Show test networks at the bottom of the dropdown, then Add network. In recent MetaMask versions you'll see two paths: Add a network from a list (curated) and Add a network manually (custom).

Choose Add a network manually. Odyssey Chain isn't on MetaMask's curated list — that's why we're adding it as a custom RPC.

Step 2 — Enter Odyssey Chain parameters

Fill in the form with these exact values:

• Network Name: Odyssey Chain
• New RPC URL: https://node.dioneprotocol.com/ext/bc/D/rpc
• Chain ID: 153153
• Currency Symbol: DIONE
• Block Explorer URL: https://odysseyscan.com

Verify the RPC URL against this page before saving. RPC endpoints occasionally change; the docs site is the source of truth.

Click Save.

Step 3 — Understand the "scam" warning

MetaMask will likely display a warning along the lines of: "This network's RPC URL or chain ID isn't on MetaMask's known list. This may be a scam."

This is not a real scam alert. It's a generic warning MetaMask shows for any custom RPC it doesn't recognize from its built-in trusted list. The warning appears for Odyssey, for Avalanche subnets, for testnets, for newly-launched chains — basically anything not on the default curated list.

If you've verified the RPC URL against this page, the warning is safe to dismiss. If you're unsure, double-check the URL character by character before proceeding. RPC verification is the only protection against unverified nodes — saving a non-matching URL routes signed transactions through unknown infrastructure.

Step 4 — Switch to Odyssey and verify your balance

Once the network is added, switch to Odyssey Chain via the network dropdown. Your 0x... address remains the same — Odyssey is EVM-compatible, so addresses are portable across all EVM chains.

Your DIONE balance should appear. If you see zero but you know you should have DIONE on this address, check OdysseyScan directly: paste your address into odysseyscan.com and confirm the on-chain balance. If OdysseyScan shows DIONE but MetaMask shows zero, the issue is MetaMask's RPC connection — try refreshing or switching networks and back.

Step 5 — Why price might display as $0

Right after mainnet launch and during early phases, MetaMask sometimes shows DIONE price as $0 even when your balance is correct. This is a price-feed display issue, not a balance issue.

MetaMask pulls price from coingecko.com or similar aggregators. If the aggregator hasn't synced the latest network state, price displays as $0 until it does. The on-chain balance is independent of the displayed dollar value.

This issue resolves on its own as price feeds sync. DIONE Wallet handles this differently — it pulls price feeds directly with appropriate fallbacks, avoiding the $0 display.

What you can and can't do with MetaMask + Odyssey

Can do:

• Send and receive DIONE
• Send and receive ERC-20 tokens on Odyssey
• Interact with EVM dApps (DiamondSwap, AmaraSwap via WalletConnect)
• Sign messages for dApp authentication

Can't do:

• Native validator delegation (no staking UI for Odyssey-native delegation paths)
• Track delegation rewards in-wallet
• Avoid the "scam" warning (it appears on every chain switch)
• Get correct DIONE pricing reliably (depends on aggregator sync)

For staking specifically, you'd connect MetaMask to the in-wallet staking dashboard via WalletConnect, which works but adds steps. DIONE Wallet integrates this directly. See How to Stake DIONE.

When MetaMask makes sense for Odyssey use

MetaMask + Odyssey custom RPC is reasonable when:

• Odyssey is one of many EVM chains you use, and switching wallets per chain isn't worth the friction
• You're already deep in MetaMask's existing setup (hardware wallet integration, multiple addresses, dApp permissions)
• Your Odyssey use is occasional rather than daily

DIONE Wallet makes more sense when:

• You hold significant DIONE balances or actively stake
• You want Odyssey-native UX without the scam-warning friction
• You're new to Odyssey and want something purpose-built rather than retrofitted

There's no universally right answer. Many users keep both: MetaMask for general DeFi, DIONE Wallet for everything Odyssey-related.

---