CustodyStress
Archive › Passphrase unavailable
Part of the CustodyStress archive of observed Bitcoin custody incidents
CS-01192

A long-term Bitcoin holder attempted to recover a Bitcoin Core wallet encrypted in 2017.

Survives
Case description
A long-term Bitcoin holder attempted to recover a Bitcoin Core wallet encrypted in 2017. The wallet.dat file had survived multiple computer migrations. The password had never been written down and the holder had relied on muscle memory. A recovery service (ReWallet) was engaged; the service ran systematic brute-force testing across all known password patterns used by the holder in 2017, including combinations with numbers and symbols. After fourteen days of GPU computation, the wallet was successfully opened. The recovery represented a common pattern: passwords set during an early adoption period, never documented, attempted years later after a significant price appreciation.
Custody context
Stress conditionPassphrase unavailable
Custody systemDesktop Software Wallet
OutcomeSurvives
DocumentationUnknown
Year observed2023
CountryInternational
Structural dependencies observed
Technical specialist required
Outcome interpretation
Access remained possible under the reported conditions.
Source
Privately Reported
Evidence type
News article
Related cases involving passphrase unavailable
217 cases involve passphrase unavailable 25 cases involve desktop software wallet View archive statistics →
This archive documents observed custody survivability failures. It does not attempt to document all Bitcoin losses or security incidents. Submit a case
← All cases
Framework references
Terms guide
Survives
Access remained possible under the reported conditions.
Constrained
Access remained possible, but only with delay, dependence, or significant difficulty.
Blocked
Access was not possible under the reported conditions.
Indeterminate
There was not enough information to determine the outcome.
Single-person knowledge
Recovery depended on information or capability held by one individual who was unavailable.
Institutional dependence
Recovery depended on a third-party institution or service that was inaccessible or uncooperative.
Documentation gap
Recovery depended on instructions that were missing, incomplete, or unclear.
Authority mismatch
The person with legal authority to act did not have operational access, or vice versa.
Original text
Rate this translation
Your feedback will be used to help improve Google Translate