Release on silence
Opens when you stop checking in for a period you choose
- How it works
- You set an inactivity period and a list of beneficiaries with shares. Each beneficiary gets a secret from you, on paper, in a will or however you like. From time to time you check in by generating an
owner_auth proof for the current day. Miss the window and the vault opens. - What the chain sees
- The vault commitment, the inactivity period, a Merkle root over hashed beneficiary secrets and shares, and the time of each check-in. Not who you are, and not who your beneficiaries are.
- Opens when
- No check-in for longer than the inactivity period (minimum 2 days, maximum 10 years).
- Notes
- Combine it with an unlock time if you want whichever comes first. You can change beneficiaries at any time before the first claim with a reconfigure proof.
Release at a time
Opens at the date and time you choose
- How it works
- You set an unlock time instead of, or as well as, an inactivity period. Recipients hold their own secrets and claim after that moment, each with a single-use claim proof.
- What the chain sees
- The commitment, the unlock timestamp and the beneficiary root. Recipients stay anonymous before and after they claim.
- Opens when
- The block timestamp reaches the unlock time.
- Notes
- Time-locked data, as opposed to funds, will use drand timelock encryption, so the ciphertext becomes decryptable at the chosen round without anyone holding a key. This part is in development.
Recover with guardians
Moves to a new key when k of your n guardians vote
- How it works
- You pick n guardians and a threshold k. Each guardian holds a secret; the registry stores only the Merkle root and k. If you lose your owner secret, you generate a new one and k guardians each submit an anonymous
guardian_vote proof for your new commitment. - What the chain sees
- The guardian root, the threshold, a running vote count per proposed new commitment, and the final rotation. Never which guardians voted.
- Opens when
- k valid votes for the same new commitment in the same round rotate the vault, which keeps its policy.
- Notes
- Any check-in or reconfiguration by the current owner cancels the round, so guardians can’t take over an active vault. Recovery is disabled once the vault has paid a claim.
Release sealed data
Hands over a decryption key after a valid claim
- How it works
- Seed phrases, private keys, documents and instructions are encrypted on your device. The ciphertext is stored on IPFS. The decryption key is split into threshold shares held by your device, your guardians and independent keepers, and is released only after a valid on-chain claim.
- What the chain sees
- Nothing about the content. The same commitment, policy and claim events as any other vault.
- Opens when
- Same as inheritance or time-lock: inactivity or unlock time, then a beneficiary claim proof.
- Notes
- Because it protects keys rather than coins, a data vault covers any asset on any chain, including chains we will never integrate natively.