Bither Desktop Wallet Application Crash: 3-Year Recovery via Password Rediscovery
SurvivedNo documentation described the custody setup — but a recovery path was eventually found.
Sygun created a Bither wallet in March 2018 holding approximately 0.019 BTC. At an unspecified point, the Bither application ceased launching entirely—double-clicking produced no response. The wallet's seed phrase and private key had been stored exclusively on a since-replaced phone and printed documentation that was lost during a house relocation, leaving no accessible backup of either credential.
For approximately two to three years, the user abandoned active recovery attempts. Upon renewed effort in early 2021, Sygun located the address.db file, which contained the encrypted private key and public receive address but no plaintext key material. Attempts to relaunch Bither by clearing the roaming folder initially succeeded, but reintroducing the address.db file caused the application to fail again—indicating either file corruption or format incompatibility with updated Bither versions.
The user explored btrecover.py but abandoned this path due to computational infeasibility of brute-forcing an entirely unknown seed phrase. The breakthrough came when Sygun recovered the wallet password ('bob123'), likely through memory or documentation not detailed in the record. Critically, Bither's standard import interface accepted only QR codes or direct private key input, not wallet files. Sygun converted the encrypted private key to QR code format, scanned it into a fresh Bither instance, and successfully decrypted it using the recovered password. Access was restored on February 11, 2021, and the user transferred the funds to Exodus wallet.
The case illustrates cascading failures in personal documentation—loss of seed phrase, loss of backup media, and application version incompatibility—offset by password recollection and creative use of the software's QR import feature. Community engagement was minimal; a moderator suggested downloading the latest Bither version and importing the file, with no substantive technical debugging offered.
| Stress condition | Documentation absent |
| Custody system | Software wallet |
| Outcome | Survived |
| Documentation | Partial |
| Year observed | 2018 |
What the absence of documentation actually removes
What documentation provides is a starting point. Without it, heirs face three unknowns before they face any access problem: does the Bitcoin exist, where is it held, and what is needed to access it. Most of this information cannot be reconstructed after the owner dies or becomes incapacitated. Educated guesses, blockchain searches, and device inventories occasionally locate wallets — but without credentials, finding the wallet does not help.
Cases in this archive where documentation was absent but recovery succeeded typically involved one of two factors: an exchange account where the heir knew the email address and could navigate the account recovery process, or a designated person who had been given credentials informally and could act. Self-custody without any documentation or designated knowledge-holder is consistently the worst combination.
The content of documentation matters as much as its existence. A note that says "my Bitcoin is in a hardware wallet in the safe" is better than nothing but insufficient. Effective documentation specifies: what type of wallet, where the seed phrase is stored, whether a passphrase exists and where it is documented, and any exchange accounts and the email addresses used. It should be tested — the executor should be able to confirm the information is accurate before it is needed.
Documentation does not need to expose credentials to be useful. A document that describes the custody structure, points to where credentials are stored, and names a person who has been briefed can be stored without security risk. The goal is not to put the seed phrase in a filing cabinet — it is to ensure the executor has a map, not a blank wall.
Translate