DigiByte Wallet v4.0.46
August 22, 2026
v4.0.45 added a way to retire a history-gap warning, and it still did not clear on the device it was written for. The reason was in the record itself.
When the wallet is not running at the moment a gap is recorded, it does not know where the gap starts — and says so honestly, which is why the warning reads “blocks below” a number rather than naming a range. The new check read that missing starting point as the number zero, and so concluded the gap might reach back to the very beginning of the chain — something no wallet can ever disprove. The warning became permanent: exactly what it was written to remove.
A gap cannot reach below the point the wallet started scanning from, because blocks before that were never its responsibility. So when the starting point is unknown, that is now used as the lower edge, and the gap can be cleared normally.
Where the starting point IS known it is still enforced strictly. A wallet whose scan began above a gap has learned nothing about it, and treating that as “all clear” is the one mistake here that could actually hide a missing transaction.