DigiByte Wallet v4.0.44
August 22, 2026
When the wallet marked a stretch of blocks as unverified, that marker could never be undone. Your only options were to let a server re-check your addresses — which hands over the whole address list this wallet exists to keep private — or rebuild the entire chain from your wallet’s creation date, re-scanning about 24 million blocks to recover twenty thousand.
That permanence was never a safety feature. It was a side effect of having no way to fetch the discarded block headers back, and it fed itself: marking a range unverified told the wallet it no longer needed those heights, so their headers were dropped to save memory, which genuinely made the range unrequestable — proving the original decision right after the fact.
The wallet now re-fetches just the headers underneath the gap and retires the marker as it goes, anchored to a checkpoint built into the app. Nothing new is trusted and no third party is involved. Headers come back a few thousand at a time, because taking a large gap in one bite risks the memory limit discarding the very headers just downloaded.
Partial progress is kept: if part of a gap cannot be fetched, the gap shrinks by whatever succeeded rather than the whole attempt failing, and it resumes after an interruption. The warning itself clears only when a gap is fully repaired — partial recovery deliberately does not clear it, because saying everything is fine while blocks are still unverified would be worse than leaving the warning up.
One known limit: a gap below block 24,000,000 cannot be repaired this way yet.