DigiWish, your will
One document per vault, allocated asset by asset, versioned on every edit, and signed onto the blockchain so its contents can be proved unchanged.
DigiWish is the will itself. It pulls your details from your profile, divides each asset between the people you name, and can be signed and anchored to the blockchain so the document can later be proved unaltered.
Three things are worth understanding before you start.
It is one document per vault, not a folder of files. Everything you allocate lives in the same will.
Every edit makes a new version. Nothing is overwritten. Version 1 stays exactly as it was, which is the point: a will is a record of what you intended and when.
Signing is separate from saving. A saved will is a draft. Signing anchors a hash of it on Polygon and delivers it to your beneficiaries' Legacy Vaults.
Creating it
There is no "create will" button, which surprises people. The will comes into existence the first time you allocate an asset and save. Until an allocation changes, the save button stays disabled.
The first save asks you to complete marital status and permanent address if they are missing. Those fields appear in the will text itself, which is why it insists.
Allocating an asset
Choose the beneficiaries for an asset and set each share. One asset can be split between several people.
Instructions and conditions
Notes attached to a specific allocation: how something should be used, when it should pass, anything the bare percentage does not capture.
Allocate the asset to someone before writing instructions on it. On an asset with no beneficiaries the form never registers as changed, the save button stays in sync mode, and the text you typed is discarded without warning.
Editing the text
Declaration, Family, Executor, Asset Manager, Guardian, Residuary and No Bond can each be edited. Saving creates a new version rather than replacing the old one.
Version history
Drafts and signed versions, in order. A signed version stays signed and stays delivered even after you edit; the edit becomes a new draft.
Downloading
Take a copy for your lawyer, your executor or your records.
Legacy Vault sync
The status pill shows whether every allocation has reached its beneficiary's Legacy Vault. The details modal breaks it down per beneficiary and per asset, so a partial sync tells you exactly which allocation has not landed.
Signing
Signing hashes the document and writes that hash to Polygon, then delivers the will to each beneficiary's Legacy Vault. Only the hash goes on-chain. The contents stay encrypted and off-chain; the hash is only enough to later prove that a document you hold is the one that was signed.
This clip runs longer than the others because the transaction is real and the app waits for it to confirm.
If the page appears to fail or logs you out during signing, check the version history before signing again. The transaction can succeed even when the interface does not say so, and signing twice writes a second hash for the same will.