[CASE.01 · WILL]
Digital will
After 18 months of silence: email instructions to your family + release IPFS-hosted documents + transfer ETH to your heirs.
[§00 — MASTHEAD]
$140B+ in crypto is lost forever to dead wallets. Yours doesn't have to be next.
Source: Chainalysis estimates ~20% of all BTC permanently lost. At current prices, ~$140B.
Some things mustexecute themselves.
Veil seals documents, transfers, and instructions on-chain — and executes them automatically when you stop proving you're alive. A will that delivers itself. A wallet that transfers itself. A secret that releases itself. Schedule the trigger, choose the recipient, sign your heartbeat every period — or stop, and the rest is automatic. Custody-free, platform-free, drand-and-Shamir-anchored.
[CONNECT YOUR WALLET TO SEAL A CALL.][SEE LIVE CAPSULES]
[STACK]
Encrypted with drand timelock · stored on Arkiv · verifiable on Braga
[§01 — CAPSULES]
Product 1 — verifiable alpha
Capsules.
Write a message today, encrypt it against a drand round that does not exist yet, store it on Arkiv with your wallet as the immutable creator. At the unlock date the round publishes; the plaintext becomes derivable to anyone with the link. The first decrypter can anchor a Reveal entity — a public, hash-only proof of decryption — so the record of WHO decrypted WHEN sits on-chain too.
[drand timelock][reveal entity][public feed][$creator immutable]
[CONCEPT — IN PICTURES]
[PROTOCOL MAP — ENTITIES + LIFECYCLE]
01[SEAL]
Seal
client encrypts plaintext against drand round N. Capsule entity goes on-chain with payload + unlock_round + creator. nothing readable until round N is published.
02[WAIT]
Wait
drand mainnet publishes rounds on a schedule. nobody can speed it up. title and creator are public so commitment is visible without disclosure.
03[VERIFY]
Verify
round publishes → key derivable in any reader's browser → plaintext recovered. first reader can publish a Reveal entity carrying only the sha-256, anchoring attribution on-chain.
[§02B — INHERITANCE VAULTS]
Beyond timestamps
Some secrets must survive you.
Cold-storage seeds. Custodial keys. The PDF in a safe nobody can open. The same primitive that locks a call until a future date can lock a secret until you stop signing — and then release it to a quorum of validators you chose. No custody. No platform risk. Just math and a heartbeat.
[M-of-N quorum][drand timelock][3 / 6 / 12 mo heartbeat][zero custody]
[CONCEPT — IN PICTURES]
[PROTOCOL MAP — ENTITIES + LIFECYCLE]
01[VAULT]
Seal
Pick a threshold (2-of-3, 3-of-5, 5-of-7), a heartbeat period (3 / 6 / 12 months), and N validator wallets. The secret is drand-timelocked and Shamir-split. One Vault entity + N Share entities go on-chain.
02[HEARTBEAT]
Heartbeat
While you're alive, you call extendEntity on the Vault every period. Only the $owner can do this — a third party can't keep a missing user's vault alive. Each extension pushes the drand round target forward. Nobody can decrypt during this window.
03[RECOVER]
Recover
If you stop signing, the heartbeat lapses. The drand round publishes. Any M of your N validators can fetch their share entities from Arkiv and combine them. The original secret is reconstructed. The exit is automatic, custody-free, and impossible to grief.
[§02C — USE CASES]
Six things Veil can execute on your behalf
Schedule what happens when you can't.
Every Vault can carry multiple triggers — emails, transfers, document drops — each with its own timer and recipient. As long as you sign your heartbeat, nothing fires. Stop signing, and the schedule runs itself.
[CASE.02 · COLD-STORAGE]
Cold-storage succession
Seed phrase split across 5 trusted wallets with 3-of-5 Shamir threshold. Heartbeat lapses → validators recover.
[CASE.03 · WHISTLEBLOWER]
Whistleblower dead-switch
If you don't check in every 7 days: deliver the PDF evidence to 3 journalists via email. Drand round publishes, contents become readable.
[CASE.04 · ANTI-COERCION]
Anti-coercion wallet
Daily heartbeat keeps your wallet under your control. Stop signing for 24h → automatic transfer to a foundation, not your captor.
[CASE.05 · EQUITY]
Conditional equity vesting
Co-founder signed-once vesting: stop signing the heartbeat → equity transfers back to the company treasury. No lawyers needed.
[CASE.06 · LEGAL]
Time-locked evidence
Sealed until the statute of limitations expires, then auto-published to the prosecutor's email + a public IPFS pin.
[§02D — TIERS]
Built to scale with your trust requirements
Four levels of personalization.
From a single self-served vault to white-glove succession planning with insurance overlay. Veil meets you where your stakes are.
[STARTER]
Self-served
One vault, up to 3 validators, Shamir recovery + heartbeat. Custody-free forever.
[PRO]
Programmable
Unlimited vaults, multi-trigger schedules, email/SMS delivery, IPFS document drops, multi-validator quorums.
[FAMILY]
Estate-ready
Legal-template overlay per jurisdiction, partner notary attestation, insurance-backed recovery, white-glove validator onboarding.
[ENTERPRISE]
API + DAO
REST API, multisig integrations, treasury succession protocols, custom validator policies, white-label deploys.
↳ Pricing announced post-mainnet. Roadmap-driven, not page-driven — talk to us if your needs don't fit a tier.
[§03 — LAUNCH]
The product
Open Veil.
Both products live in the same app. One nav, two sections. The capsule feed is the public face. Inheritance vaults are private to their owner + their chosen validators. You stay in control of which one you use, and when.
[§06 — WHY ARKIV]
The pieces no centralized DB can give you.
[01] Immutable authorship
Every entity has a $creator stamped on-chain at creation. Cannot be edited, cannot be spoofed. Sell or transfer ownership later — the original author stays known forever.
[02] Differentiated expirations
Capsules live up to a year past their unlock. Reveal markers live 90 days. Subscriptions auto-renew via extendEntity. Lifecycle as a first-class type, not an afterthought.
[03] Queryable relationships
Reveal entities link to Capsule entities via shared-attribute keys. No foreign keys, no joins — just indexed predicates that resolve in O(log n).
[04] Verifiable, end to end
Every create, update, and delete returns a tx hash on Braga. Anyone can replay the history in the block explorer without trusting Veil at all.
Open sourceNo server holds keysdrand timelock encryptionTx-verifiable on Braga