Skip to main content
LifeWyn

The mechanism, honestly

A dead man’s switch is a good idea built on one shaky assumption

The assumption is that silence means death. It usually doesn’t — and the release it sets off is the one kind of mistake you can never take back.

A dead man’s switch does something reasonable: it watches for signs of life, and when they stop for long enough, it hands over what you left behind. It is old, it is simple, and it needs nobody’s permission — which is exactly why it appeals.

The trouble is what it can actually see. It can see that you did not open an email. From that one small fact, it has to decide whether to do something permanent.

Where it breaks

Four failures, all of them ordinary

It can't tell a quiet week from the end of a life

A timer knows one thing only: that nothing happened. A long stay in hospital, a phone lost on a trip, a place with no signal, a month too heavy to open an app, a break you took on purpose — to a countdown they all look the same. And every one of them can end with your most private things landing in someone's inbox.

The wrong call can't be taken back

A release that comes late is an inconvenience. A release that comes wrongly can never be undone: a seed phrase that has been seen has been seen, a letter meant for after you're gone read while you're still here. The two mistakes are not the same size — and a plain timer treats them as if they were.

It asks you to keep proving you're alive

The whole thing only works while you keep checking in. Miss enough messages and it fires; switch it off because you're travelling and it guards nothing at all. Both happen all the time, and both are you quietly losing an argument with your own safeguard.

It hands over the keys just as the hard part begins

A switch delivers credentials and stops there. It never says which bank, which policy, what to claim or in what order, or which form to sign. Dropping a set of passwords on a grieving family is not the same thing as helping them.

What LifeWyn requires instead

Seven stages. Only the last one opens anything.

Your silence still starts the process — it is a genuinely useful signal. It just is not allowed to finish it.

  1. Life as usual

    Discloses nothing

    You open the app, unlock with a fingerprint, tap now and then to confirm you're here. Nothing is pending. Nothing is watching you in any way you ever have to think about.

  2. You miss a check-in

    Discloses nothing

    Nothing happens except a quiet reminder to you, on the channels you chose. Almost every time, this is the whole story — you see it, you open the app, and it's over.

  3. The reminders grow more insistent

    Discloses nothing

    More attempts, more channels, a longer window to answer. Still no one else is contacted. Still nothing is revealed.

  4. The people you trust are asked

    Discloses nothing

    The contacts you named are asked one gentle question: are you alright? They are never shown your vault. Their answer on its own changes nothing — it is a signal, not a verdict.

  5. Verification opens a case

    Discloses nothing

    Evidence is gathered and scored, fraud checks included. Only a genuine, many-signal result is accepted, and even then it is cross-checked by a separate service rather than believed on sight. Anything uncertain resolves to no.

  6. Any waiting period you set runs its course

    Discloses nothing

    A time lock is a rule you set yourself, per item and per person: this opens to this someone no earlier than this moment. Where you set one, even a verified result waits it out — which is how a wrong answer stays reversible for as long as waiting costs nothing.

  7. Your wishes are finally carried out

    Discloses

    Item by item, person by person, with every delay and condition you set honoured. Each key share is decrypted on the recipient's own device — the server never puts your key back together.

Every gate in that chain fails closed: when a check cannot be completed, the answer is no. That imbalance is deliberate — a release that waits can be put right, and a release that should never have happened cannot.

Questions

The ones people actually ask

Is LifeWyn a dead man's switch?
It has one at its heart, and it refuses to stop there. Noticing your silence is only the first stage — the thing that starts a conversation, never the thing that ends it. What sets LifeWyn apart is that silence is never enough on its own: corroboration and scored verification stand between the quiet and any disclosure, and every one of those gates fails closed.
What if I am simply travelling or off-grid?
Then you get reminders, and you clear them by opening the app — that is all. You set the check-in intervals yourself, and you can tell the system in advance about a stretch when you will be unreachable. At no point does an unanswered notification disclose anything.
What if I am unconscious in hospital for weeks?
That is the exact case a plain switch handles worst, and it is why hospitalisation and incapacity are their own states here, with their own rules. Someone can be given your medical directives and emergency contacts without a single part of your estate being opened. Death is not the only condition this system understands.
Could someone trigger it deliberately to get at my data?
The chain never begins with someone else's say-so — it begins with your own missed check-ins, and you end it by logging in. Beyond that, verification is scored rather than asserted: a scripted burst of submissions, an unverified or tamper-flagged document, or more than one active case all raise fraud risk against the confidence score, and a single contact saying you are fine caps it outright. The release gate is then cross-checked by a service that takes nothing on trust, and every step is audited.
Is a plain switch ever the right choice?
Yes. If all you want is for a seed phrase not to die with you, and you can live with the false-alarm risk, a simple switch is cheap, predictable and needs nobody's cooperation. It is a real trade-off, and we would rather say so than pretend there is only one honest way to build this.

Set the conditions yourself

Check-in intervals, channels, who gets asked, what waiting period applies to which item, and who receives what. All of it is yours to decide.