CustodyStress
Archive › Device loss
Part of the CustodyStress archive of observed Bitcoin custody incidents
CS-01263

Device lost — Trezor (2024)

Survives
Case description
A 2024 case involved a traveller whose luggage—including a Trezor Model One hardware wallet—was lost by an airline. The holder had their seed phrase documented at home. They purchased a new Trezor, restored using the seed phrase, and transferred funds to a different address within 48 hours as a precaution against the lost device being found and subjected to physical attack. The case was a successful recovery demonstrating the seed phrase system working as designed—but it also required the holder to act quickly and know the correct recovery procedure.
Custody context
Stress conditionDevice loss
Custody systemHardware wallet (single key)
OutcomeSurvives
DocumentationUnknown
Year observed2024
CountryInternational
Outcome interpretation
Access remained possible under the reported conditions.
Source
Privately Reported
Evidence type
News article
Related cases involving device loss
188 cases involve device loss 274 cases involve hardware wallet (single key) 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.