DigiByte Wallet v4.0.76
August 30, 2026
Please update. An independent security audit, reading the wallet’s code, found that coming back to the app from the launcher or the Recents screen showed the wallet with no PIN asked. Leaving the app did lock it, but nothing sent the screen back to the PIN page when you returned, so the wallet you had left was still there. Opening the app fresh asked for the PIN as it should, which is why this was not noticed in ordinary use. The maintainer reproduced it on a test phone: home button, a few seconds on the launcher, tap the icon, and the Send screen was reachable with a live Send button. On a phone with no fingerprint enrolled, a send could have gone through from there. Someone who picked up your unlocked phone in that state could have moved coins, approved a Digi-ID login, swept funds, or paired a node. It was found by reading the code, not from a report of lost funds, but it was real, and it is fixed: the wallet now returns to the PIN screen every time it is locked, and pressing Back from that screen leaves the app rather than revealing what is behind it.
Sending now always asks for your fingerprint or PIN, on every phone. Before, phones without a strong fingerprint sensor had no check at all on a DGB or DigiDollar send, and several actions had no check on any phone. One shared gate now covers every DGB, DigiDollar and DigiAsset send, every Digi-ID approval, every funds sweep, Hub login and node pairing: fingerprint first if you have one, otherwise the in-app PIN, and if the sensor is locked out after too many tries you fall through to the PIN rather than being refused. The auto-lock timeout in Settings, which was saved but never actually read by anything, now works: leave the wallet open and untouched for the time you chose and it locks itself.
Smaller hardening from the same audit. Screenshots and screen recording are blocked while you type a recovery phrase or passphrase, and the keyboard is told not to learn those words or offer them as suggestions later. The Community Hub session token was being written to the phone’s debug log and stored in plain text; it is no longer logged and is now encrypted at rest, and wallet addresses are no longer logged either. Android’s device-transfer and cloud-backup tools are now explicitly told to leave every piece of wallet data alone. Some old, unused code paths that handled the seed as text were removed, and the security documentation was corrected wherever it described a protection the code did not actually have.
This release also completes the scheduled security review, due every ten releases. The automated checks on the published app came back clean: no known vulnerabilities across its 227 software dependencies, no secrets built into the app, every network address it contains accounted for, and the standard protections switched on in the native code. Also in this release: wallets that used the “S…” wrapped-segwit address format can now be swept in the recovery tool, verified on mainnet, where before they were found but could not be moved.