Introduction

A dead man's switch is one of the oldest safety concepts in engineering. In its simplest form, it is a mechanism that triggers when a human operator stops actively holding it. Trains, heavy machinery, and military systems have used dead man's switches for decades. The logic is straightforward: if the operator is incapacitated, the system should respond automatically. This same logic can be applied to Bitcoin to solve one of its most pressing problems: inheritance.

How a Dead Man's Switch Works

The concept is elegant in its simplicity. You perform a regular action that signals you are alive and present. If you stop performing that action, the system assumes you are gone and executes a predetermined response.

In software, this might be as simple as checking in periodically. You send a message, click a button, or perform a transaction on a regular schedule. The system monitors for that signal. As long as the signal arrives, nothing happens. When the signal stops, the system activates.

The key insight is that no one needs to know you are dead. No death certificate is required. No legal process is triggered. The absence of your active participation is the only signal the system needs.

Applying Dead Man's Logic to Bitcoin

Bitcoin is programmable money. Every transaction includes spending conditions that define who can spend the coins and under what circumstances. This programmability means the dead man's switch logic can be embedded directly into how the Bitcoin is held.

The idea is to create a spending condition that says: the owner's key can spend these coins at any time, but a second key (held by the heir) can also spend them, but only after a specific time has passed without the owner taking action.

As long as the owner periodically refreshes the timelock by moving the coins to a new address with a fresh countdown, the heir's key remains dormant. When the owner can no longer perform this refresh, whether due to death, incapacitation, or any other reason, the clock runs out and the heir's key activates.

Why Miniscript Makes This Possible

Bitcoin has always had a scripting language that allows programmable spending conditions. But that language, called Script, is notoriously difficult to work with. Writing complex conditions in raw Script is error-prone and hard to verify.

Miniscript is a structured subset of Bitcoin's Script language that makes complex spending conditions practical to implement. It is readable enough for developers to work with, processable by wallet software, and expressive enough to encode the dead man's switch logic cleanly.

With miniscript, you can define exactly the conditions described above: an owner key that works immediately, an heir key that activates after a time delay, and the ability to refresh the timer by moving coins to a new output with the same conditions.

No Trust Required

What makes this approach powerful is that it requires no external parties. There is no inheritance service to trust. No lawyer holding sealed envelopes. No company that might go out of business. The dead man's switch lives entirely within Bitcoin's own system, enforced by the same consensus mechanism that secures every transaction.

The coins and their conditions are secured by Bitcoin itself. Nothing external can interfere with the inheritance plan once it is set up. The only requirement is that the owner periodically signals they are alive by moving their coins.

Conclusion

A dead man's switch is a proven concept adapted for a new purpose. By embedding this logic into Bitcoin's programmable spending conditions through miniscript, inheritance can be handled entirely on-chain, without trusting anyone, without involving the legal system, and without any single point of failure.