Release notesDIONE Wallet Release Notes
Release notes and security advisories. Updates are auto-pushed to installed wallets after cryptographic verification.
Release 1.0.1 · May 2026DIONE Wallet 1.0.1 — Initial public release
DIONE Wallet 1.0.1 is the initial public release, shipping the BUILD feature set after Hacken audit completion on 20 February 2026 (9.5/10, 0 critical, 0 high, 1 medium, 1 low).
What's in 1.0.1
- Native staking UI with validator picker (sortable by uptime, commission, total stake)
- Hardware wallet support: Ledger, Trezor, and direct Tangem NFC integration
- Migration verifier — paste your old ERC-20 address to confirm migrated balance
- DEX deep-link integration (DiamondSwap, AmaraSwap)
- Validator delegation flow with in-wallet rewards tracking
- Portfolio price feeds with direct fallbacks (no $0 display issue)
- Explorer deep-link to OdysseyScan for every transaction
- WalletConnect v2 for dApp connectivity
- Cryptographically signed auto-update with binary signature verification
- Turkish UI strings (TR locale)
- Address book for repeat sends
- Hacken security audit complete: 9.5/10, 0 critical / 0 high findings
How DIONE Wallet writes release notes
Every DIONE Wallet release ships with a structured changelog following industry conventions for software release documentation. Three principles guide the format.
What goes in a release noteEach entry covers what changed (specific feature, bug fix, or security patch), why it matters (user-visible impact), and any required user action (most updates are zero-action via signed auto-update). Cosmetic changes that don't affect user experience are intentionally not included — they create noise without informing decision-making.
Versioning conventionDIONE Wallet uses semantic versioning (MAJOR.MINOR.PATCH). Major bumps indicate breaking changes (rare; would require user re-import). Minor versions add features without breaking existing flows. Patch versions are bug fixes and security patches. The current version, 1.0.1, indicates one patch since the v1.0 mainnet-companion release in November 2024.
Security advisoriesIf a vulnerability is discovered post-audit, the project's commitment is responsible disclosure with reasonable patch turnaround. Advisories are published here alongside regular release notes, with a CVE reference where applicable, the affected version range, and the upgrade recommendation. The auto-update prompt explicitly flags security vs feature releases so users can prioritize.
Why changelog quality mattersA changelog is the operational documentation of a wallet's behavior over time. For a self-custody wallet handling user funds, transparency is non-negotiable — users need to know whether the auto-updater changed signing behavior, whether new permissions are requested, and whether security posture has shifted. The Hacken-audited security page covers the 1.0.1 audit baseline; this page documents everything since.
How to verify a releaseThe canonical release source is the download page. Each installer is code-signed; signed auto-update verifies signatures before applying. If a release appears here that does not appear on the download page (or vice versa), treat as suspicious and verify via the security page before installing.
Subscribing to release notificationsThere is no email release-notification service at 1.0.1. Users with version monitoring needs can watch the GitHub repository at https://github.com/dione-wallet for release announcements.
How updates work
Auto-updateSigned binary verification
DIONE Wallet checks for new releases on launch. Each update binary carries a cryptographic signature; the wallet verifies the signature against a pinned public key before applying.
If signature failsUpdate is rejected
A failed signature check rejects the update entirely. Your current version continues running. Tampered binaries cannot replace the running wallet.
Verify manuallySettings → About
Open Settings → About inside DIONE Wallet to confirm the running version. The current stable release is 1.0.1.