DigiByte Wallet v4.0.86

October 4, 2026

Please update. The first launch after the update rebuilds your transaction history from the blockchain once. Your coins and recovery phrase are untouched; the balance fills in as the scan catches up, and Send is available when it finishes. On a wallet with a long history this can take an hour or more. If a send is still waiting to confirm, the rebuild waits for it, for up to 14 days.

A DigiAsset send now checks every coin it spends with the DigiAsset indexer before anything is signed: each must hold exactly the asset being sent, in the amount the wallet recorded. The coins come from one address and the asset change goes back to that address. If the indexer cannot be reached, the send waits instead of guessing. Moving assets out of another wallet applies the same check.

DGB that sat on the last output of a DigiAsset transfer is released for spending once the wallet proves that output carries no asset units.

Block headers are now refused unless they carry their proof of work, and each header's difficulty target is checked against DigiByte's MultiShield rules. For now that check only records mismatches; a later release enforces it.

The compact-filter scan follows the chain through the short reorganisations DigiByte sees every day, and a wallet whose history goes back more than about a year no longer stalls partway through its scan. Peers are no longer dropped over the wallet's own state.

With Tor on, everything the app sends waits for Tor and goes direct only after the wallet has told you Tor is unavailable. Background sync dials through Tor, the Market says it is outside Tor before it loads, and turning Tor off clears the "Tor unavailable" banner. Every connection to DigiScope uses the same pinned certificates.

DigiAsset screens, from issue #101: quantities use plural forms in every language, a transaction's details lead with the asset and quantity, the confirmation shows the markers and total the send will pay, activity rows keep their label on one line, and UTXOs Held counts only coins that hold units. "Scan for missing funds" reports against the coins the wallet itself holds.

Six native test suites were added, 101 in all, running on every change to the code and once a week.