DigiByte Wallet v4.0.71
August 29, 2026
Each DigiAsset moves in its own transaction, and two transactions cannot spend the same coin. A wallet holding fifty assets and a single DGB output could therefore move exactly one asset and strand forty-nine, because the change from each transfer goes to the destination wallet and never comes back to fund the next. The only remedy was to deposit DGB into a wallet you were trying to leave. That shape is common, not hypothetical.
Recovery now splits the DGB first into one output per asset, waits for a single confirmation, re-scans, and then moves every asset. It waits rather than chaining unconfirmed transactions, which the network would reject in bulk; it re-scans rather than predicting, because the chain is the authority on what the split produced; and it never splits more than once, so no bug can loop on someone’s money. If the wait times out nothing is lost: the split pays the source wallet’s own addresses, and a later run simply finds the outputs. The amount needed is stated up front, before anything is signed.
Proven on mainnet: three assets against a single output, all three moved after a 19-second split, remainder swept. The size of each split output is derived by actually building the transfer it will fund rather than from a chosen constant — that guess has been wrong here once before — and the check caught a real under-sizing error the first time it ran. This release also records which restore paths have been proven on real funds, and adds a tool for building test wallets on older derivation schemes no current software will create.