Bridge DIONE Between Chains — Wanchain Setup Guide for DIONE Coin

If your DIONE is currently on Ethereum, Polygon, or another EVM chain, here's how to bring it to Odyssey Chain via Wanchain.

Last updated: 2026-05-03

---

Bridging vs migration — clarifying the terms

This confuses people. Two related but distinct operations:

Migration (one-time, November 2024): The DIONE token launched as an ERC-20 token on Ethereum in 2023. When Odyssey Chain mainnet went live in November 2024, the project ran a one-time migration converting all ERC-20 DIONE balances to native DIONE on Odyssey at a 1:1 ratio. After migration was completed, the ERC-20 token was deprecated.

Bridging (ongoing): Cross-chain movement of native DIONE between Odyssey and other chains. This works through bridge contracts that lock tokens on one chain and mint a representation on the other. Bridges like Wanchain operate continuously; you can bridge DIONE in either direction whenever you want.

If you're thinking "I have ERC-20 DIONE in my MetaMask from before mainnet, how do I get it migrated?" — that's the migration article: How to Migrate DIONE from ERC-20 to Odyssey.

If you're thinking "I have native DIONE on Odyssey and want to bridge it to Ethereum to use in some DeFi protocol there" — that's this article.

Why would I bridge DIONE off Odyssey?

Several legitimate reasons:

To use in DeFi on other chains. Some DeFi protocols (lending, yield aggregators) operate on Ethereum or Layer 2s and don't have Odyssey deployments. To use DIONE as collateral or in a yield strategy on those chains, you'd bridge to the relevant chain.

To trade on exchanges that only list the bridged version. If a CEX lists "DIONE on Ethereum" but not native Odyssey DIONE, you'd need to bridge to deposit there. This is rare since most exchanges support direct native DIONE deposits, but occasionally happens.

To pay or settle in environments expecting Ethereum-side tokens. Some payment processors or merchant integrations work with Ethereum-side ERC-20 tokens and don't yet support Odyssey native deposits.

Legitimate reason check: if you can't articulate a specific reason, you probably don't need to bridge. Native DIONE on Odyssey is the canonical form of the token; bridging adds friction and a small risk surface (bridge contracts have historically been a target for exploits).

Why would I bridge DIONE TO Odyssey?

The more common case for current holders:

You hold "DIONE" or "wrapped DIONE" on Ethereum, Polygon, or another chain that you didn't intend to. This usually happens because:

• You bought from a DEX that listed a wrapped DIONE token on Ethereum without realizing it was a wrapped version
• You participated in a cross-chain liquidity program that issued wrapped DIONE
• You held ERC-20 DIONE pre-migration and didn't migrate during the migration window — in this case, the wrapped or legacy form may still exist on Ethereum

To consolidate holdings. If you have small amounts of DIONE on multiple chains for whatever historical reason, bridging brings them together on Odyssey where staking and other native features work.

To use Odyssey-native features. If your DIONE is on a wrapped form on another chain, you can't stake, can't use the validator picker, can't participate in OBOL — those are Odyssey-native operations.

Step-by-step: bridging via Wanchain

Wanchain is the official bridge partner. The flow:

Step 1 — Open Wanchain bridge

Go to bridge.wanchain.org (or whatever the current Wanchain interface is — verify against wanchain.org if uncertain).

Step 2 — Connect DIONE Wallet

Click "Connect Wallet" → choose WalletConnect → DIONE Wallet's WalletConnect QR or deep-link will appear.

In DIONE Wallet, approve the connection request. The wallet should now be visible in Wanchain's UI.

Step 3 — Select source chain, destination chain, asset

For a bridge to Odyssey:

• Source chain: Ethereum (or wherever your wrapped DIONE currently is)
• Destination chain: Odyssey (or "DIONE Chain" depending on Wanchain's labeling)
• Asset: DIONE

For a bridge from Odyssey:

• Source chain: Odyssey
• Destination chain: Ethereum (or wherever you want to send)
• Asset: DIONE

Step 4 — Enter amount and recipient

The recipient address defaults to your connected wallet address (which is the same on both chains since both are EVM). If you're bridging to send to a different address, override the default.

Wanchain will display:

• Source chain fee (gas + bridge fee)
• Destination chain fee (gas to mint on destination)
• Estimated time to completion (usually 5-15 minutes)

Step 5 — Approve and sign transactions

Bridging usually requires two transactions:

1. Approval — authorize Wanchain's bridge contract to spend your DIONE
2. Bridge transaction — actual lock-and-mint

Sign both via DIONE Wallet's connected session.

Step 6 — Wait

The transaction confirms on the source chain (~30-60 seconds for Odyssey, ~3-5 minutes for Ethereum), then the bridge waits for sufficient confirmations, then mints on the destination chain. Total time: 5-15 minutes typical.

Wanchain's UI should show the progress with a transaction tracker. If the UI shows "completed" but you don't see balance on the destination chain after 5 minutes, check the destination chain's block explorer manually using the transaction hash from Wanchain's tracker.

Step 7 — Verify on destination

Switch DIONE Wallet to the destination chain (network selector). Your bridged DIONE should appear in the balance. If it doesn't auto-detect, you may need to manually add the DIONE token contract address for that chain.

For DIONE on Ethereum, the canonical contract address is documented in the project's bridge documentation. Always verify the contract address against the official source — fake DIONE tokens on Ethereum exist and can be socially engineered into your wallet via "add this token" prompts from compromised sites.

Common errors and fixes

"Insufficient balance for gas" — you need a small amount of the source chain's native token (DIONE for Odyssey, ETH for Ethereum) to pay gas. Add gas funds before bridging.

"Approval failed" — usually a gas estimation issue or temporary network congestion. Wait a minute, try again.

Transaction stuck pending for >30 minutes — gas price was too low for current network conditions. Most wallets allow you to "speed up" a stuck transaction by replacing it with a higher gas price; check DIONE Wallet's transaction history for a speed-up option.

Bridge UI shows "completed" but balance not visible on destination — manually verify with the transaction hash on the destination chain's block explorer. If the mint transaction completed but the wallet doesn't show the balance, it's a wallet display issue (try refreshing or re-adding the token) rather than a bridge failure.

Funds appear on a different address than expected — check what address you specified as the recipient in step 4. If you bridged to your own wallet's address, the funds are there but on a different chain than you're currently viewing — switch chains in DIONE Wallet to confirm.

Risks and what to know

Bridge contract risk. Bridges are smart contracts that hold significant value. They've historically been the most-exploited part of DeFi infrastructure (Wormhole, Ronin, BNB bridge — all hit for hundreds of millions). Wanchain has a longer track record without major exploits than many alternatives, but the risk isn't zero.

Wrapped token risk. When you bridge DIONE to Ethereum, what you receive is "wrapped DIONE" — a representation token whose value depends on the bridge contract working correctly. If the bridge contract fails, the wrapped tokens may become worthless even though the original Odyssey DIONE is fine.

Fee surprises. Cross-chain transactions involve gas on both chains plus bridge fees. The total can be unpredictable on high-congestion days. Check the fee estimate before signing — if it looks unreasonable (e.g., 50% of the amount being bridged), wait for less congested conditions.

Reversal complexity. Bridging in one direction takes 5-15 minutes. Reversing it takes another 5-15 minutes plus another round of fees. Double-check the direction and amount before signing.

Should you bridge at all?

Honest answer: in most cases, no.

If you hold native DIONE on Odyssey and you want to use it for:

• Staking → don't bridge, stake natively
• Trading → use a CEX with DIONE listed (MEXC, Gate.io, Bybit, Crypto.com)
• DeFi on Odyssey-native protocols (DiamondSwap, AmaraSwap) → don't bridge, use them directly
• Sending to someone → don't bridge, send native

The cases where bridging is worthwhile are narrow: specific DeFi yield strategies on other chains that aren't available on Odyssey, settlements with merchants who only accept Ethereum-side tokens, or consolidating wrapped DIONE that ended up on other chains accidentally. If you're not sure, you probably don't need to bridge.

---