Skip to content

Promote to production: Digital Legacy Letter (Legacy category) - #117

Merged
slaveofcode merged 2 commits into
mainfrom
develop
Aug 2, 2026
Merged

Promote to production: Digital Legacy Letter (Legacy category)#117
slaveofcode merged 2 commits into
mainfrom
develop

Conversation

@slaveofcode

Copy link
Copy Markdown
Owner

Promotes #116 — encrypted client-side legacy letter (AES-256 + Shamir family shares), new Legacy category, bilingual + OG.

Kresna and others added 2 commits August 2, 2026 09:32
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
feat(legacy): Digital Legacy Letter (encrypted 'in case I die' vault)
@slaveofcode
slaveofcode merged commit 45b521a into main Aug 2, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant