Illustrated scenarios
Case files.
The circuit diagrams on the home explain the protocols. These pages show what the protocols feel like in practice. Two case files: one for Capsules (a crypto analyst who stopped editing their record), one for the Inheritance protocol (three pictures of a cryptographic dead-man's switch).
Case file — meet K-31, an analyst who got tired of editing their own history
Singapore · paid newsletter · 340 → 890 subscribers · December 12, 2024 · 03:47 UTC
K-31 stopped trying to be right. They started being verifiable instead.
K-31 is a 31-year-old crypto analyst in Singapore. Wire-rimmed glasses, kitchen office, 340 paying subscribers at $19/mo. Their problem isn't analysis — it's trust. Every call they get wrong, somebody screenshots it and tags them three weeks later. Every call they get right, three influencers claim they called it first. Their churn is 8% monthly and climbing. The market doesn't reward being right anymore. It rewards being able to prove you were right.
THE NIGHT THEY SEALED THEIR FIRST CALL
December 12, 2024, 03:47 UTC. K-31 writes "BTC over 95K before January 16" plus a 600-word thesis: macro setup, on-chain flows, where they're wrong if X happens. They don't tweet it. They seal it in Veil instead, public, unlock January 16. The body is encrypted client-side against a future drand round nobody — including K-31 — can read yet. The title, their wallet, and the unlock timestamp go on-chain. Everyone can see they committed. Nobody can see what.
[OUTCOME]
January 16. BTC closes at 92K. Call fails.
K-31 cannot delete it. The cipher unlocks on schedule. The thesis becomes public, verbatim, with the on-chain creation timestamp anyone can verify on Braga. K-31 publishes a post: "I was wrong. Here's why my model missed." They expect the worst. Their churn that month drops to 3%. Three months later they're at 890 subscribers. The market did not reward being right. It rewarded being unable to lie.
Protocol illustrated
Three pictures of a cryptographic dead-man's switch.
Wax seal + hourglass + envelopes — the same metaphors a notary used a hundred years ago, now encoded as drand timelock and Shamir threshold on a public-database chain.
[01 — VAULT]
The vault entity, sealed with a wax sigil. Drand-timelocked at creation; only $owner can call extendEntity to push the unlock further into the future.
[02 — HEARTBEAT]
Each heartbeat period, the owner turns the hourglass over (signs an extendEntity tx). The cardiogram keeps pulsing. The drand round target rolls forward; the vault stays sealed.
[03 — RECOVERY]
If the owner stops signing, the round publishes. Three of the five named validators open their envelopes, combine their Shamir shares, and the original document reconstructs in the center.