The short answer: a true zero-knowledge vault is one the company cannot read. That is the point of it while you are alive. It is also the problem when you die, because a server that holds no key cannot unlock anything for your family. BlockWill resolves this by separating two things that other tools bundle together: who holds the decryption key (handed over in person during the BlockWill Ceremony) and when the encrypted data is delivered (released by VaultRelay only when your conditions are met). Your crypto, passwords and instructions reach the people you chose, and the key never touches the cloud.

What is the zero-knowledge inheritance paradox?

Every digital estate tool has to answer one question: when the owner is gone, how does the family get in?

There are two common answers, and both have a hole.

  • The server holds a key. The platform keeps a copy of your decryption key, or a recovery key, so it can release your data to your heirs later. That means your most sensitive information is readable by the company, by anyone who breaches it, by a rogue employee, and by anyone with a subpoena, every day you are alive.
  • Only you hold the key. The platform encrypts everything on your device and never sees the key. Nobody can read your vault, including the company. But when you die, nobody can open it either. Your heirs inherit a file they cannot decrypt.

For years the choice was security now or access later. You could not have both from one product.

How BlockWill resolves it

BlockWill, headquartered in the Dubai International Financial Centre, splits the two halves of access so that neither the server nor any one person can open the vault alone.

1. Client-side encryption and an in-person key handover: the BlockWill Ceremony

Every record you add to BlockWill is encrypted on your own device with AES-256 before it reaches a server. BlockWill never holds your key. We wrote about this in Client-side encryption: why BlockWill's servers never see your will.

Instead of a cloud backup of the key, you run a guided Ceremony while you are alive:

  • You hand a physical key, a YubiKey or a BlockWill Secret, directly to the Beneficiary or Guardian you have chosen.
  • The Ceremony records a witnessed chain of custody: who received the key, when, who was present, and where it is kept.
  • Holding that key gives the person nothing yet. The encrypted vault has not been delivered to them, so there is nothing to open.

2. Conditional delivery of the ciphertext: VaultRelay

Your encrypted vault stays locked on BlockWill's regional infrastructure (you choose the data region at sign-up: India, the UAE, the United States, Africa, Singapore or Japan) until VaultRelay's release conditions are met. Those conditions can combine:

  • Executor confirmation. A named Executor, such as your lawyer or wealth adviser, confirms the event.
  • Inactivity timers. Scheduled check-ins with a cooldown period, so a missed holiday check-in does not release anything. You, or your Executors, can stop a false trigger before anyone receives a thing. The mechanics are in VaultRelay: a trustless inheritance trigger.

Once the conditions are met, BlockWill's servers transmit the encrypted payload to the Beneficiary. Only when that payload meets the physical key from the Ceremony, on the Beneficiary's own device, does decryption happen. The server sends ciphertext it cannot read to a person who could not open it before. Both halves are needed, and neither half is useful alone.

Why this matters beyond the paradox

Self-custody crypto. A seed phrase cannot be recovered by a bank, an exchange or a probate court. BlockWill lets you document recovery instructions and fragment them across roles without any third-party server seeing the phrase. See Making sure your family can access your crypto and What happens to your crypto when you die.

Five roles instead of one emergency contact. Consumer tools usually have a single "trusted contact". BlockWill separates Asset Owner, Asset Manager, Executor, Beneficiary and Guardian, so the person who confirms a death is not the person who receives the assets, and the person who holds a key is not the person who can trigger a release. That maps onto how a legal will actually works.

A tamper-evident record: DigiWish. Your DigiWish, the record of what you own and what you intend, is hashed and timestamped on the Polygon blockchain. Anyone can later prove the document existed at that moment and has not changed, without anything private being written on-chain. How to check it yourself: How to verify your document hash in DigiWish.

How this compares with the alternatives

Each category below solves part of the problem. The comparison is based on each product's public documentation as of November 2026; check the current terms before relying on any of them.

Password managers with emergency access (1Password, Bitwarden)

  • Who holds the key: You. The emergency contact gets an encrypted copy of your key after a waiting period.
  • What triggers release: A request from the contact plus a time delay you set.
  • What it covers: Logins and notes.
  • The gap: One contact, one delay, no executor, no record of intent, nothing for property, accounts or crypto that are not logins. Setup guide: Emergency access setup.

Platform legacy tools (Apple Legacy Contact, Google Inactive Account Manager)

  • Who holds the key: The platform.
  • What triggers release: Inactivity, or a death certificate plus an access key.
  • What it covers: That one platform's data.
  • The gap: Covers only Apple or only Google. Nothing outside the platform, and the platform decides what the contact can see.

Digital estate services with server-side keys (Everplans, GoodTrust and similar)

  • Who holds the key: The service, or the service plus you.
  • What triggers release: A deputy requests access and the service unlocks it.
  • What it covers: Documents, logins, wishes.
  • The gap: Convenient, but the company can read the vault, so the data is exposed to breach, insider access and legal demands while you are alive.

Crypto multisig custody (Casa, Unchained)

  • Who holds the key: Split between you, the provider and a recovery key.
  • What triggers release: A signing quorum.
  • What it covers: Bitcoin and a few chains.
  • The gap: Strong for coins, silent on everything else: bank accounts, property, documents, instructions.

BlockWill

  • Who holds the key: A person you chose, handed the key in a witnessed Ceremony. The server never holds it.
  • What triggers release: VaultRelay: executor confirmation and inactivity timers with a cooldown, under your rules.
  • What it covers: Property, financial accounts, crypto, documents, instructions, across five roles.
  • The gap: Requires one in-person handover while you are alive. That is the trade we chose over a cloud key.

The short version: password managers and multisig solve custody but not estates. Legacy-contact tools solve one platform. Estate services solve the estate but hold the key. BlockWill holds no key and still delivers.

Frequently Asked Questions

Can BlockWill employees or a hacker decrypt my vault?

No. Data is encrypted on your device with AES-256, and the key is handed over in person during the Ceremony, never uploaded. BlockWill's servers store ciphertext only. A breach of the server yields files that cannot be decrypted without the physical key your Beneficiary holds.

My Beneficiary already has a YubiKey from the Ceremony. Can they open my vault early?

No. The key is half of the equation. The encrypted vault is not delivered to them until VaultRelay confirms your release conditions, such as executor sign-off or an inactivity trigger that has passed its cooldown.

No. A will decides who inherits under the law. BlockWill makes sure your executors and heirs can find and unlock what the will refers to. DigiWish is a timestamped record of intent that your lawyer can turn into a will that meets local law.

Where this goes

Most of what a family needs after a death is not money. It is knowing what exists, where it is, and how to get in. Sticky notes, a spreadsheet on a laptop, or a vault the company can read are the three ways that information usually travels today. None of them is good enough for a seed phrase, and none of them survives a server breach.

Hardware-backed client-side encryption, a witnessed key handover, and conditional delivery of ciphertext are not exotic ideas on their own. Putting them in one system, with separate roles for the people who confirm, hold and receive, is what makes zero-knowledge and inheritance compatible.

If you want to see the handover and the release in practice, the walkthrough at blockwill.io/walkthrough shows both, and the demo at demo.blockwill.io lets you run the Ceremony yourself.


This article describes BlockWill's architecture as of November 2026. It is general information, not legal advice. BlockWill is a wealth continuity platform, not a law firm.