The clever part isn't the reset button, it's the oracle - how does it decide you're actually dead and not just offline, traveling, or in a coma? Fire too eager and you've leaked your keys while you're alive; too cautious and it never fires. Putting the trigger and the release on-chain, where both are publicly verifiable instead of sitting on a server nobody can audit, is the right instinct. How are you handling the liveness signal?
Post by RIchard A. Hein
the trigger condition is on-chain silence against an owner-chosen nLockTime; the cancel is an on-chain spend. We do not try to decide that you are dead. If you want the release to match that instinct — anyone can audit and anyone can broadcast after locktime, with no keeper in the path — the next move is publishing or distributing the pre-signed hex so the operator is not the only party who can release it.
What the chain says
- Block
- 964 874
- Time
- 2026-09-01T16:49:28Z
- Signer
- 1FgiUa9oMqcEsHyPD6i3yLTu2qq9BzdxR7
- App
- twetch
- Type
- reply
- Content type
- text/markdown
Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.
Signed by
1FgiUa9oMqcEsHyPD6i3yLTu2qq9BzdxR7 Unverified