DigiByte Wallet v4.0.81
September 21, 2026
Please update. This release comes out of a scheduled, line-by-line review of the wallet and of the C library underneath it, not from any report of lost funds. It tightens how the wallet handles data it receives from other nodes on the network — transactions, block headers, compact filters and scripts — and it does so identically on 32-bit and 64-bit phones.
The checkpoints bundled with the app are refreshed, and the way they are produced has changed: every compact-filter checkpoint is now recomputed and proven against the chain before it is allowed into a release. Restoring a wallet with an older birthday no longer stalls part-way through its scan.
The amount you approve is the amount that is signed, everywhere. DigiDollar amounts are read by a strict cents parser, the DigiAsset confirmation is written from the quantity the wallet actually parsed, and a lone comma is read as the decimal point in the DigiDollar and DigiAsset screens as it already was for DGB.
DigiAssets are looked after more carefully. Every output an incoming transfer assigns to you is set aside as soon as the wallet sees it, and again immediately before any send is built. DigiDollar transfers are recognised whichever standard script framing the sender used.
Ten native test suites were added with this work, 82 in all. They run on every change to the code and once a week, because some of what they guard goes stale with time rather than with commits.
A note on downloading: some browsers scan a newly published APK after the download has finished, and can sit at 100% for a while before they hand the file over. That is the browser, not the file. You can check any copy against the SHA-256 published with the release.