A will tells your family what they receive. It rarely tells them what you wanted to say. The password to the vault is useful. The sentence you never got around to saying out loud is the thing they will keep.

DigiWish is the part of BlockWill built for that second thing. It lets you write messages now and have them delivered later, to specific people, at a moment you choose. A letter to your daughter that arrives on her wedding day. A voice note for your partner released the week after you are gone. Instructions that only make sense once a particular event has happened. Until that moment, the message is encrypted on your device, and no one, including BlockWill, can open it.

This post explains what DigiWish is, how the encryption keeps your words private until the right time, and how delivery actually works.

What is DigiWish?

DigiWish is BlockWill's time-released messaging feature. You compose a message (text, an attached document, or a recorded note), choose who should receive it, and choose when. The "when" can be a fixed calendar date, a recurring date such as a birthday, or a triggering event such as confirmed inheritance through VaultRelay.

The message is encrypted in your browser before it is stored, using the same client-side approach as the rest of BlockWill. Your words never reach our servers in readable form. What we hold is an encrypted blob and the delivery rule that says when to release the decryption key. We can see that a message exists and when it is scheduled. We cannot see what it says.

Why time-released, and not just stored

A stored message is available the moment someone has access. A time-released message respects timing as part of the meaning. There is a difference between your son finding a letter while clearing out a drawer and that same letter arriving, deliberately, on the morning of his first day as a father.

Timing also protects the message. A note that contains sensitive instructions (where a physical asset is, how to handle a delicate family matter) should not be readable the day you write it and forget about it. By binding release to a date or an event, DigiWish keeps the content sealed until the context you intended for it actually exists.

How the encryption works

When you write a DigiWish message, your browser generates a fresh encryption key for that message and encrypts the content locally using AES-256-GCM, the same authenticated cipher SecureVault uses. Authenticated means the ciphertext carries a tag that proves it has not been altered. If a single byte changes in storage, decryption fails loudly instead of returning something corrupted.

The message key itself is then wrapped (encrypted again) so that it can only be unwrapped under the release condition you set. For a fixed date, the key is held under a time lock enforced by BlockWill's release service. For an inheritance event, the key is wrapped so that it can only be released through the same VaultRelay process that governs your vault, which means a confirmed triggering event, not a guess and not an early peek.

The recipient does not need a BlockWill account before you write to them. When the release condition is met, they receive a secure link and are guided through a lightweight verification step (a one-time code to their email or phone) before the message is decrypted in their browser. The plaintext appears for them, and only them, at the moment it was meant to.

What BlockWill can and cannot see

This is the part worth being precise about, because it is the part people worry about.

BlockWill can see that you created a message, how large it is, who the intended recipient is, and the release rule. We need those to deliver it. BlockWill cannot see the contents of the message at any point, because the content is encrypted on your device with a key we do not hold in usable form before release. We do not read your messages to improve a product, we cannot hand them to anyone who asks, and a breach of our servers would expose encrypted blobs, not your words.

When the release condition fires, the wrapped key is released to the verified recipient's session, and decryption happens in their browser. The plaintext lives in their device's memory, not on our servers.

Setting up your first DigiWish

From your dashboard, open DigiWish and choose New Message. You write or record the message, then attach any files you want included. Next you pick the recipient by name and contact detail. Then you choose the release rule: a specific date, a recurring date, or an inheritance trigger tied to VaultRelay.

Before you save, DigiWish shows you a plain summary: who it goes to, what triggers it, and a reminder that you can edit or revoke it any time while you are still active. You stay in control. A message is not a decision you are locked into. It is a draft to your future, and you can revise it as your life changes.

A note on tone and trust

We built DigiWish carefully because the feature touches grief. The product gets out of the way. There are no streaks, no nudges to write more, no gamified prompts. You should never feel marketed to while writing to someone you love. The interface is quiet on purpose.

That restraint extends to delivery. A DigiWish message arrives once, cleanly, with a short and human explanation of what it is and who it is from, so a grieving recipient is never confused about why a stranger's platform is emailing them. The first thing they see is your name, not ours.

Frequently Asked Questions

What is DigiWish?

DigiWish is BlockWill's time-released messaging feature. You write a message now and choose when it is delivered, whether a fixed date, a recurring date such as a birthday, or after a confirmed inheritance event. The message is encrypted on your device until the moment it is released.

Can BlockWill read my DigiWish messages?

No. Each message is encrypted in your browser with AES-256-GCM before it is stored. BlockWill holds an encrypted blob and the delivery rule, not the contents. The message is only decrypted in the verified recipient's browser when the release condition is met.

What can trigger a message to be sent?

Three kinds of trigger: a fixed calendar date, a recurring date, or an inheritance event confirmed through VaultRelay. You choose which when you create the message.

Does my recipient need a BlockWill account?

Not in advance. When a message is released, the recipient gets a secure link and verifies their identity with a one-time code before the message decrypts. They do not need to have signed up beforehand.

Can I edit or cancel a message after writing it?

Yes. While you are active, you can revise, reschedule, or revoke any DigiWish message at any time. Nothing is locked in.

What happens if I attach a document to a DigiWish?

The attachment is encrypted with the message using the same client-side process. It travels sealed and is only decrypted for the verified recipient at release time, exactly like the text.

Is a DigiWish message legally binding like a will?

No. DigiWish is for messages, wishes, and instructions, not for legal succession. Your legally operative documents belong in your will and SecureVault. DigiWish carries the human part: the words, context, and guidance that a legal document does not hold.

Further reading: