feat(legacy): Digital Legacy Letter (encrypted 'in case I die' vault) - #116
Merged
Conversation
A new client-side tool + 'Legacy' category. Write a private letter (final words + account passwords) that family can open only when the time comes. - Content encrypted with a random 256-bit DEK (AES-256-GCM). The DEK has two independent recovery paths: a PBKDF2-derived password wrap, and a Shamir Secret Sharing split over GF(256) into N family shares needing any K (e.g. 3 of 5). - Pure, unit-tested libs: shamir.lib (8 tests), crypto.lib, vault.lib (12 tests) — round-trips both paths, rejects wrong password/insufficient shares, share checksum + tamper detection, file never contains the shares. - Thin Create/Open island; 'unrecoverable by design' warning; executor-share tip. - EN + Bahasa SEO content (ID: 'Surat Wasiat Digital', no 'alat'). Auto /id/ + category hub + OG image via existing pipeline. status: beta. Note: true auto-release-on-death isn't possible purely client-side (needs a server holding data); handoff is human-arranged via the password/shares by design. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ubfx4XocHcECaL8twp9zsr
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
goodwebtools | dd24592 | Aug 02 2026, 02:37 AM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
New client-side tool + Legacy category. Write an encrypted letter — final words + account passwords — that family opens only when the time comes.
Security (all in-browser)
Why not auto-release on death
A purely client-side tool can't detect death without a server holding your data — so handoff is human-arranged via the password/shares (the honest, zero-infrastructure trigger). Documented in the FAQ.
Verify
npx vitest run→ 624 passed (20 new: shamir 8 + vault 12, real WebCrypto round-trips) · lint 0 errors · build 183 pages (EN+ID tool, EN+ID category hub, OG image).