Chain settings you do not have to guess, in a wallet built for Odyssey from the start.
| Platform | Requirements | File |
|---|---|---|
![]() |
Windows 10 (1909) or later, 64-bit | dione-wallet-v4.5.9.exe |
| macOS 12 or later | dione-wallet-v4.5.9.dmg |
|
| x64, Ubuntu 20.04 or later, or equivalent | dione-wallet-v4.5.9.zip |
Checksums for every file are on the v4.5.9 release page.
Warning
Only download from this GitHub release page. A mirror, a search advertisement or a file sent in a chat is not the project.
The chain ID in the guide does not match the one the application expects, and the network that results resolves to nothing. Six digits, one wrong character, and an interface that looks configured but cannot fetch a block. Most of the confusion around a new chain is not the chain at all; it is a settings panel where four fields have to agree with a source you trust.
That is the argument for a wallet that already knows the network it was built for. DIONE Wallet ships Odyssey Chain configured, with chain ID 153153 and the RPC and explorer it needs, so the first launch is a wallet rather than a setup exercise. Other EVM networks can still be added by hand, and the application asks for all four fields and reports when they do not resolve, which is more than most panels do.
Getting the network right is the difference between a wallet and a form. Once Odyssey Chain is configured, everything the chain offers is available without a second tool.
- Odyssey Chain ready at install, with the explorer one click from the balance.
- Custom networks accepted through name, RPC URL, chain ID and symbol, with the chain ID treated as the exact field it is.
- Staking, validator data and reward tracking that only appear because the network is understood, not guessed at.
- Signed builds with published checksums, so the configuration you trust is the configuration that runs.
A note that saves an afternoon: a chain ID that is one digit off does not produce an error message that mentions the chain ID. It produces an empty balance and a spinner, which is why the guides here start with the explorer rather than with the application. Read the address on the chain's own explorer, compare the number it reports with the number in the settings panel, and the whole class of problem collapses into one correction.
This repository is the chain-configuration side of Odyssey Chain, and this page is one of the wallet's pages rather than a description of it.
| Guide | What it answers |
|---|---|
| Add Another Network to DIONE Wallet | The four fields, filled in order, with the chain ID called out as the exact one. |
| How Odyssey Chain Powers DIONE | Chain ID 153153, the RPC endpoint, the explorer and the validator set behind the chain. |
| DIONE Wallet Stuck on Connecting | When a configured network still will not answer, and what to remove first. |
| Odyssey Chain Gas Fees Inside DIONE Wallet | What the network charges for gas, and why the wallet adds nothing on top of that fee. |
The phrase is the wallet. A network setting is public information and a phrase is not; no chain configuration screen has any reason to ask for the words.
A network that would not resolve becomes a chain you can use. The balance appears, the explorer link in the wallet opens the same address, and the staking screens stop being empty because the application finally knows which chain it is talking to.
The lesson from the settings panel is worth keeping after it works. Every field in a network entry is checkable against the chain's own documentation, and a wallet that already ships the right values removes four chances to mistype one of them. That is the reason the first launch here is a wallet rather than a form.
- Odyssey Chain arrives configured, with the chain ID and endpoint already correct.
- Other EVM networks are added deliberately, with the chain ID treated as exact.
- The explorer is one click from the balance, which is where a wrong setting shows up first.
- It is the field that has to match exactly, and a single wrong digit produces a network that looks configured and fetches nothing.
Yes. Any EVM network is accepted through its name, RPC URL, chain ID and symbol, and the wallet keeps them as separate entries rather than replacing Odyssey Chain.
Because the address on that network has no history yet, or because the chain ID does not match the endpoint. Check the address on that chain's explorer before changing anything else.
Release questions and bugs go to the dione-desktop-wallet issue tracker. Report a vulnerability through a private security advisory on the same repository.
MIT


