Original text
Rate this translation
Your feedback will be used to help improve Google Translate
Reference library for Bitcoin custody survivability. Independent reference memos, structural pattern analysis, and framework reference architecture.
This library documents observed Bitcoin custody conditions, failure patterns, and survivability gaps. The materials are descriptive and non-advisory. They do not provide instructions, recommendations, or custody guidance.
Applicable to anyone who holds Bitcoin in any form — exchange accounts, hardware wallets, multisig setups, or managed custody — whether for themselves, their family, or their clients.
What stress surface, failure surface, survivability, silent invalidity, and other terms mean in this library.
Where custody creates gaps in estate plans, probate, fiduciary duty, and professional competence.
Every tool that touches your Bitcoin knows something about how it is held. A comparison of what nine tool types collect, retain, or expose about your custody setup.
What each professional or product covers, what they do not, and where gaps form between them.
Invisible expectations about backups, heirs, attorneys, devices, and time that nobody checks until something goes wrong.
How independent diagnostic layers have historically emerged in systems where multiple parties depend on shared infrastructure without a neutral reference between them.
Independent reference memos documenting observed Bitcoin custody behaviors, dependencies, and failure conditions.
Lawyers, financial advisors, accountants, and trustees face distinct fiduciary obligations when clients hold Bitcoin in self-custody. Standard professional frameworks assume custodial intermediaries, centralized account structures, and reversible transactions — none of which apply to Bitcoin held directly. These memos document where professional duty of care intersects with custody infrastructure that professionals cannot inspect, verify, or control.
Bitcoin custody creates a structural divide between legal authority and technical access. A power of attorney may grant decision-making rights over digital assets, but it does not provide a seed phrase. A will may name an executor, but the executor may lack the knowledge, credentials, or device access to move funds. These memos document the gap between what legal documents authorize and what custody systems actually require — including POA activation timing, trust language enforceability, estate document completeness, and authority conflicts across multiple parties.
When custody responsibility shifts — through death, incapacity, divorce, or family transition — the technical access chain must survive independently of the original holder. Bitcoin inheritance risk is not primarily a legal problem; it is an access continuity problem. These memos document executor access gaps, spouse survivability under various custody configurations, incapacity modeling when cognitive decline or sudden unavailability removes the key person, and the structural requirements for a custody system to function after its architect is no longer available.
Bitcoin custody systems rely on external dependencies that are rarely enumerated and almost never tested. A hardware wallet requires firmware from a vendor. A multisig configuration requires coordination across multiple signers. A backup strategy depends on the physical integrity of a location, the availability of a password manager, or the continued operation of a cloud service. These memos document the hidden dependency chains, shared failure surfaces, single points of failure, vendor risks, and coordination requirements that determine whether a custody system actually functions when it is needed — or silently degrades until recovery is attempted.
Every custody product — hardware wallets, managed custody services, collaborative custody, exchange accounts, Bitcoin ETFs — has a coverage boundary where its protection ends and the user's unprotected exposure begins. These boundaries are rarely documented and often misunderstood. Wallet interfaces create impressions of safety that may not correspond to the underlying custody conditions. Service terms can change unilaterally. Providers can discontinue operations. These memos document the coverage limits of specific custody product types, the structural gap between what products claim and what they deliver, and the failure surfaces that emerge when users rely on implied protections that do not exist.
Custody systems are not tested by normal conditions. They are tested by death, divorce, natural disaster, device failure, coercion, prolonged incapacity, and institutional collapse. Most custody configurations that appear functional under routine use contain structural weaknesses that only surface under stress — when a spouse cannot locate a seed phrase, when an executor is blocked by a cosigner timeout, when a hardware wallet fails during an emergency, or when a court demands proof of control that no document provides. These memos model specific failure scenarios and document how custody systems behave when the assumptions they were built on no longer hold.