Dead Man's Switch

What Is a Dead Man's Switch?

A dead man's switch is a mechanism that automatically executes a predetermined action when its owner fails to provide periodic proof-of-life signals within a configured timeframe. In cryptocurrency, this typically means transferring digital assets to designated heirs or releasing encrypted recovery information to beneficiaries.

The concept originates from physical safety devices in heavy machinery and trains that activate when the operator becomes incapacitated. In crypto, the mechanism addresses a fundamental problem: unlike bank accounts or brokerage holdings (which are tied to identity and recoverable through legal channels), cryptocurrency ownership is proven exclusively through control of private keys. If a holder dies without sharing their keys, the assets become permanently inaccessible. The blockchain does not recognize court orders, death certificates, or probate proceedings.

This makes crypto inheritance uniquely difficult compared to traditional assets. A dead man's switch provides a trustless or trust-minimized fallback: if the owner goes silent, the system ensures their assets reach the intended recipients without relying on lawyers, courts, or third-party custodians.

How It Works

Every dead man's switch follows a four-stage lifecycle, regardless of the underlying implementation:

1. Configuration: the owner sets a check-in schedule (for example, every 90 or 365 days) and designates beneficiaries
2. Heartbeat: the system sends periodic reminders, and the owner confirms they are alive by clicking a link, signing a transaction, or performing some other action
3. Grace period: after a missed check-in, escalating notifications are sent before activation to prevent accidental triggering
4. Execution: after the grace period expires without response, the predetermined transfer or data release occurs automatically

The critical design challenge is balancing convenience against security. Too-frequent check-ins create friction that owners may abandon. Too-rare check-ins leave assets in limbo for extended periods after death. Most implementations use intervals of 3 to 12 months.

Bitcoin Timelock Approach

Bitcoin supports dead man's switches natively through two script opcodes: OP_CHECKLOCKTIMEVERIFY (CLTV) for absolute timelocks and OP_CHECKSEQUENCEVERIFY (CSV) for relative timelocks. CSV is preferred for dead man's switches because the timer resets whenever coins move to a new address, creating a natural "heartbeat" mechanism. For a deeper exploration of these opcodes, see Bitcoin Timelocks: CLTV and CSV Explained.

The canonical Bitcoin dead man's switch uses a branching script structure:

OP_IF
  <Owner's pubkey> OP_CHECKSIG
OP_ELSE
  <365 days> OP_CHECKSEQUENCEVERIFY OP_DROP
  <Heir's pubkey> OP_CHECKSIG
OP_ENDIF

This script creates two spending paths. The owner can spend the funds at any time using the IF branch. The heir can only spend using the ELSE branch after the timelock expires. To "stay alive," the owner periodically sends their coins to a new address (even back to themselves), which creates new UTXOs and resets the relative timelock. If the owner dies and stops moving funds, the timelock eventually expires and the heir can claim the coins.

Pre-Signed Transaction Approach

An alternative Bitcoin method avoids custom scripts entirely. The owner creates a standard transaction paying designated heirs, sets an nLockTime value for a future date, signs it, and gives the signed transaction to heirs or a service. The transaction is valid but cannot be broadcast until the locktime expires.

To extend the timer, the owner simply spends the referenced UTXOs in a normal transaction. This permanently invalidates the pre-signed inheritance transaction since the inputs no longer exist. The owner then creates a new pre-signed transaction with an updated locktime. Services like Bitcoin Legacy automate this rolling process.

Ethereum Smart Contract Approach

Ethereum smart contracts can implement dead man's switches directly in Solidity. The typical architecture involves three core functions:

// Simplified dead man's switch contract
contract DeadMansSwitch {
    address public owner;
    address public beneficiary;
    uint256 public lastCheckIn;
    uint256 public timeout;

    function checkIn() external {
        require(msg.sender == owner);
        lastCheckIn = block.timestamp;
    }

    function claimAssets() external {
        require(msg.sender == beneficiary);
        require(
            block.timestamp > lastCheckIn + timeout
        );
        payable(beneficiary).transfer(
            address(this).balance
        );
    }
}

The owner calls checkIn() periodically to reset the inactivity timer. If the timeout elapses without a check-in, the beneficiary can call claimAssets() to transfer the contract balance. Account abstraction (ERC-4337) has made this pattern more accessible by allowing smart contract wallets to embed dead man's switch logic directly into their validation rules, rather than requiring a separate external contract.

Multisig with Decaying Thresholds

The most mature approach combines multisig with timelocks to create "decaying" spending conditions. A wallet might require 3-of-3 signatures normally, but after one year of inactivity it relaxes to 2-of-3, effectively granting heirs the ability to spend without the owner's key. This pattern is enabled by Miniscript, which allows complex spending policies to be expressed safely in Bitcoin Script. For more on how multisig wallets work, see Bitcoin Multisig Wallets Explained.

Wallets like Liana (by Wizardsardine) and Nunchuk implement this natively. Nunchuk's 2026 Taproot Multisig beta uses Taproot, Schnorr signatures, and MuSig2 to make inheritance transactions indistinguishable from regular single-sig transactions on-chain, preserving privacy.

Use Cases

Crypto Inheritance

The primary use case is ensuring heirs can access cryptocurrency after the owner's death. Unlike traditional assets that pass through probate, crypto has no institutional recovery mechanism. An estimated 2.3 to 3.7 million BTC (roughly 11 to 18% of Bitcoin's maximum supply) are believed permanently lost, with a significant portion attributed to holders who died without sharing access. The QuadrigaCX collapse in 2019, where C$250 million in customer crypto became inaccessible after the CEO died, highlighted the scale of this problem (though it was later determined to be fraud). For a comprehensive guide to planning around these risks, see Bitcoin Inheritance Planning Guide.

Business Continuity

Organizations holding crypto in cold storage face a similar problem when key holders become unavailable. A dead man's switch ensures that corporate funds remain accessible if the designated signer leaves the company, becomes incapacitated, or is otherwise unavailable. Collaborative custody services like Casa and Unchained use multisig combined with timed recovery procedures to address this.

Whistleblowing and Data Release

Beyond asset transfer, dead man's switches can release encrypted information. Sarcophagus, a decentralized protocol built on Ethereum and Arweave, enables users to encrypt data and configure automatic release if the owner stops periodically "re-wrapping" it. Third-party node operators (called Archaeologists) stake tokens as collateral to guarantee they will decrypt the outer encryption layer at the configured time.

Comparison to Traditional Estate Planning

Most experts recommend a hybrid approach: combining on-chain mechanisms (timelocks, multisig) with off-chain legal documents such as notarized agreements that recognize the on-chain conditions.

Risks and Considerations

Premature Triggering

Extended hospital stays, travel without internet access, or simply forgetting a check-in can trigger a dead man's switch while the owner is still alive. Multi-channel reminders (email, SMS, push notifications) and extended grace periods help mitigate this risk, but they cannot eliminate it entirely. Setting the check-in interval too short increases the chance of accidental activation; setting it too long leaves assets inaccessible for extended periods after actual death.

UTXO Management Complexity

Bitcoin timelock-based switches require the owner to periodically move their coins to reset the timer. This creates ongoing transaction fees and operational overhead. Unchained's analysis of Miniscript timelock wallets found they incur 13 to 38% higher transaction fees due to additional script data per input. There is also a fee rate risk: if Bitcoin transaction fees spike when the timelock is about to expire, the owner faces a choice between paying high fees to reset or letting the inheritance condition activate.

Heir Preparedness

A dead man's switch is useless if heirs do not know how to claim the funds. Heirs may lack the technical knowledge to import recovery scripts, operate Bitcoin wallets, or interact with smart contracts. They need functional wallets configured in advance, clear instructions, and ideally some practice with the recovery process. Outdated beneficiary designations (ex-partners, estranged relatives) create additional complications.

Service and Protocol Risk

Centralized dead man's switch services introduce a single point of failure. If the service shuts down, the check-in mechanism stops working and funds may be released prematurely or become permanently locked. On-chain solutions (using timelocks or smart contracts) are more resilient because the rules are enforced by the blockchain itself, but they require more technical expertise to set up. Some protocols that launched with significant funding, such as Sarcophagus (which raised $5.47M from VCs), have seen declining activity, highlighting the longevity risk of relying on any single project.

Privacy Exposure

Standard Bitcoin scripts expose the inheritance structure publicly on-chain. Anyone analyzing the script can see that a dead man's switch exists and identify the heir's public key. Solutions using Taproot address this by hiding unexecuted spending conditions: if the owner spends normally via the key path, the alternative heir path is never revealed. Only when the heir actually claims funds does the script path become visible.

Why It Matters

Experts project trillions of dollars in crypto assets will need to transfer via inheritance in the coming decades. As self-custody adoption grows and Bitcoin's value increases, the stakes of getting inheritance right grow proportionally. Dead man's switches represent one of the most practical tools for bridging the gap between crypto's permissionless, keyless-recovery design and the human reality that everyone eventually becomes unable to manage their own keys.

Layer 2 protocols and modern wallet architectures are making these mechanisms more accessible. Miniscript-enabled wallets automate the complex script construction. Taproot preserves privacy. Collaborative custody services reduce the technical burden on both owners and heirs. The trend is toward making dead man's switches a standard wallet feature rather than a specialized tool.

This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.