DigiByte Wallet v4.0.41
August 20, 2026
The wallet learns which blocks concern it from compact block filters, and it checks the chain of those filters against a set of pinned checkpoints. Until now that check only watched — a peer serving a chain that disagreed with a checkpoint had its data accepted anyway, and the disagreement was written to a log. Now it acts: a batch of filter headers that crosses a checkpoint is verified BEFORE it is accepted, and if it diverges the batch is rejected, the peer is banned, and the wallet asks someone else. Bad data is never written down in the first place.
Two related weaknesses are closed with it. A single lying peer can no longer pull you onto its version of the chain — if your chain matches a checkpoint, that is proof it is the real one, and a peer disagreeing with it is now the peer’s problem. And honest disagreement no longer causes a false alarm: rebuilding from a peer now requires an agreeing majority of at least three, instead of any two peers disagreeing, which could happen during an ordinary reorganisation of the chain.
If the wallet cannot verify the chain at all — every peer disagreeing, or a network-level attack isolating you — it stops at the last point it did verify and tells you, rather than carrying on with data it cannot check or freezing with no explanation. Anything already found below that point stays visible.
One honest limit worth stating: this protects the chain below the newest checkpoint (now height 24,050,000, roughly 13,000 blocks from the tip instead of 260,000). The most recent blocks are still trusted on first sight and confirmed by peer agreement. If you want that last stretch verified too, pair your own DigiByte node — that remains the strongest setting available.