What is a dead man's switch?
Originally an engineering safety term, a dead man's switch is a mechanism that activates when the operator stops being active. On a train, it cuts the engine if the driver lets go. In software, it triggers a predefined action if the user stops responding.
For crypto and digital estate planning, a dead man's switch does this:
"If I haven't logged in or responded for X days, assume something has happened to me, and deliver these instructions to the following people."
It's the missing piece between "I have a secure crypto setup" and "my family can actually access my assets if I'm gone."
Why crypto specifically needs this
Traditional financial assets have built-in dead man's switches: banks require death certificates, courts handle estate distribution, lawyers manage wills. The system assumes you might die and has processes for it.
Crypto has none of that. The blockchain is completely indifferent to whether you're alive. Your wallet doesn't know you died. It doesn't trigger any process. It just sits there, inaccessible, forever.
The only person who can initiate a transfer is the person who holds the key. If that person is permanently unavailable, the assets are permanently locked.
A dead man's switch solves this by creating an automated "if I go silent, do this" instruction that runs without you.
How a crypto dead man's switch works
A good implementation has three phases:
Phase 1: Normal operation
You log in, interact with the system occasionally. The timer resets with each interaction. Nothing happens.
Phase 2: Inactivity check
After a configured period of silence (e.g., 90 days), the system sends you a check-in email: "Are you still there?"
You click the link → timer resets, nothing happens.
You don't respond → the system waits a bit and sends another reminder.
Phase 3: Trigger
If you don't respond after the maximum number of reminders, the system assumes something has happened and delivers your pre-configured message to your emergency contact.
That message contains: how to decrypt your vault, the questions to answer, the decryption tool, and the permanent location of your encrypted data.
What a dead man's switch should NOT do
This is where most implementations fail: it should not transmit your private keys or seed phrases.
A poorly designed system might store your actual seed phrase and email it to your family when triggered. This creates enormous risks:
- Email is not secure — anyone who intercepts the email gets your seed phrase
- Email providers can be hacked — your seed phrase is now permanently in someone's servers
- The stored data is a target — the system holding your seed phrase is worth attacking
A well-designed dead man's switch uses zero-knowledge architecture: the encrypted data is stored, but even the system storing it can't read it. Only someone with the correct answers to the knowledge-based questions can decrypt it.
Your family receives: the questions, the location of the encrypted data, and the decryption tool. They don't receive: your keys.
Configuring the right trigger timing
The trigger timing is a balance between two failure modes:
Too sensitive: The switch triggers when you're just on vacation, hospitalized temporarily, or traveling without internet. Your family panics unnecessarily, and you receive notifications you didn't want.
Too slow: By the time the switch triggers, months have passed. Time-sensitive assets (business credentials, access codes that expire) may be useless.
A reasonable default for most people:
- Initial waiting period: 90 days (you'll almost certainly check in at least once in 90 days)
- Reminder interval: 7 days (once the check-ins start, you get a week between each)
- Maximum reminders: 3 (after 3 missed check-ins, something is probably wrong)
Total: 111 days from your last activity before the trigger fires.
This can be adjusted based on your lifestyle. If you regularly travel to areas without internet for extended periods, extend the initial window. If you're in a high-risk occupation, shorten it.
What your emergency contact receives
When the trigger fires, your emergency contact should receive:
✅ The key schema — which questions were used to derive the encryption key, and in what order
✅ The question text — the actual question(s) they need to answer
✅ The TxID — where your encrypted vault is stored
✅ A decryption tool — ideally an offline HTML file they can download and run locally
✅ Step-by-step instructions — written in plain language for someone who may not be technical
They should NOT receive the answers to the questions. That's the zero-knowledge part — the system never knew the answers.
The offline decryption requirement
One detail that matters enormously: your family should be able to decrypt your data even if the platform no longer exists.
If your dead man's switch solution requires logging into a specific website or app to decrypt, and that company shuts down, your family is back to square one.
A good solution:
- Stores the encrypted data on a permanent, decentralized network (like Arweave) with a permanent URL
- Provides a standalone HTML file for decryption — no account needed, no server needed, runs in any browser
This way, even if the company behind the switch disappears, your family still has everything they need.
Setting one up today
You don't need to be technical to set up a crypto dead man's switch. The basic steps are:
- Decide what information to protect — seed phrases, wallet types, recovery procedures
- Choose your knowledge-based questions — things your emergency contact already knows
- Encrypt and store — ideally with a solution that uses permanent storage
- Configure the trigger — set your timing preferences
- Designate your emergency contact — and optionally tell them they're designated (they don't need to know the answers, just that they might receive instructions one day)
- Test it once — make sure the check-in emails work and you know how to respond
The whole process takes about 20 minutes. The peace of mind is indefinite.
PingVaults implements all of the above: zero-knowledge encryption in your browser, permanent Arweave storage, configurable inactivity switch with check-in emails, and an offline HTML decryptor for your emergency contact. Set up your vault →