Crypto inheritance planning
Prepare a wallet inventory, recovery sequence and plain-language instructions for one trusted person. Keep sensitive files encrypted and release the handoff only after the check-in and safety periods pass.
Encrypted before upload · Email check-ins · A separate safety period · One intended recipient per delivery
The practical gap
The hard problem is not only preserving a seed phrase. The recipient must identify the correct wallet, understand any passphrase or multisignature policy, locate compatible hardware, avoid scams, satisfy legal obligations and know which action should happen first. A useful inheritance plan documents that sequence without turning one stored file into an easy theft target.
What the service actually does
Explain the wallet type, network, hardware, passphrase model, multisignature participants and the location of each required recovery factor.
A single seed phrase plus a complete wallet map can become a single point of theft. Decide whether the delivery should contain the secret, one factor, or only directions to independently controlled material.
Simple offers assisted recovery after authorised release checks. Private requires the separate recovery code you control and can reduce provider-side recovery capability.
Technical possession of a key is not the same as legal entitlement. Identify the executor, adviser and records that establish authority before the recipient moves assets.
Important boundary: ZeroLatch does not hold, transfer or monitor cryptocurrency; execute a smart contract; verify death; provide custody; or give a recipient legal ownership. It delivers selected information after the configured inactivity process.
How it works
Record the asset type, network, wallet and recovery method without creating an unnecessary balance list.
Decide where the seed, passphrase, device and ZeroLatch recovery code will live.
Define unfamiliar terms, first actions, scam warnings and the professional contact.
Recover a test wallet on a clean device and correct every ambiguous instruction.
Go deeper
Build the inventory, backup and recipient rehearsal in a safe order.
Read guidePlan for the device, seed, optional passphrase and recipient skills.
Read guideTurn specialist knowledge into instructions another person can follow.
Read guideQuestions before you start
It depends on the threat model. Storing the complete wallet map and every recovery factor together can create one theft target. Many plans store context and directions separately from at least one independently controlled secret.
No. ZeroLatch delivers information. It does not hold a wallet, sign a transaction, name a legal beneficiary, interact with a smart contract or determine who owns the assets.
Recovery generally depends on the compatible recovery words and any optional passphrase, not merely the original hardware. Exact procedures and supported standards can change, so verify them with the wallet manufacturer and test using a non-critical wallet.
No. Secret sharing can add redundancy, but it also adds operational complexity and compatibility risk. Use it only if every participant understands storage, thresholds, replacement and recovery testing.
Use a separate low-value wallet. Have the intended recipient follow the written instructions on a clean device while you observe, then remove assumptions and record any software or hardware dependency.
Create a draft, review the recovery path, and activate only when the recipient, timing, and contents are right.
Create a test delivery