DigiByte Wallet v4.0.84
September 27, 2026
Please update. Like the last three releases, this one comes out of the scheduled, line-by-line review of the wallet and of the C library underneath it, not from any report of lost funds. It is about how far the wallet can be misled about the chain.
Every block header the wallet accepts now has its proof of work computed for its own mining algorithm (SHA-256d, Scrypt, Skein, Qubit, Odocrypt, and Groestl for older blocks), and the wallet checks which algorithms the network allowed at that height. In this release the check runs in an audit mode that records any disagreement without rejecting headers; a full sync against the live chain produced none. Enforcement follows in a later release.
The height the wallet syncs toward is now agreed by the peers you are connected to, not taken from whichever peer claimed the most. One peer can no longer keep the wallet showing Syncing or keep Send disabled.
Every send now gets exactly one answer: accepted, rejected, cancelled or confirmed. A transaction a peer rejects as invalid is reported as such, and the wallet no longer re-announces sends that are already confirmed, which it used to do in the background every 90 seconds.
Newly mined coins are counted only once they have matured, and DigiDollar balances count only outputs from after the DigiDollar activation height. The list of peers the wallet starts from is now fetched over the same certificate-pinned connection as the rest of DigiScope, including by the background sync worker.
Six native test suites were added with this work, including one built from 55 real block headers from both networks, 94 in all, running on every change to the code and once a week.