ADR: per-device envelopes instead of shared ciphertext

Branch: Open your PR against dev. PRs targeting main are closed automatically.

Description:
Write docs/adr/0001-per-device-envelopes.md using the template from #320. Record the decision to store one message_envelopes row per recipient device rather than a single shared ciphertext per message: what was considered, why it was chosen, and the costs accepted (storage growth, the envelope GC job, sibling-device enforcement on send and edit).

Acceptance criteria:

Follows the ADR template: context, decision, alternatives considered, consequences, status
Reconstructs the alternatives and reasoning from the codebase and the issue history (Multi-device self-sync (sender's own other devices) #188, Migrate send_file_message and ask_assistant to ciphertext + envelopes #337), citing them
Consequences include the operational costs and link to services/envelopeGc.ts and lib/messageFanout.ts
Notes that MLS group messages are the exception (one ciphertext for the whole group) and links to the next ADR

@maxx-GENIUS

@maxx-GENIUS has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

Ready to ship immediately! Focus: Full-Stack Software Engineering & Core Architecture for "ADR: per-device envelopes instead of shared cipher". Plan: Deliver clean, modular code following the repository's established design patterns and TypeScript/Rust conventions. Guaranteed 100% green CI & test coverage. Zero hand-holding. SLA: clean PR in 1-2h. Track record: 166+ merged PRs in Web3 (OSS score 83, Top 2%).

ℹ️ Repo Maintainers: To accept this application, review their application or assign @maxx-GENIUS to this issue.

⚡ Protocol Implementation Blueprint & Production Readiness Proposal

Hi @maintainers, I am ready to implement and ship this issue immediately.

I have reviewed the repository architecture and pre-analyzed the execution path for this task so you don't have to spend any time onboarding or hand-holding:

1. Scope & Execution Boundary

Target Domain: Full-Stack Software Engineering & Core Architecture
Target Issue: ADR: per-device envelopes instead of shared ciphertext
Architectural Scope: Review codebase conventions, architectural structure, and requirements for ADR: per-device envelopes instead of shared ciphertext.

2. Implementation Strategy & Invariants

Deliver clean, modular code following the repository's established design patterns and TypeScript/Rust conventions.
Preserves backward compatibility and strict type invariants across existing public APIs and internal interfaces.

3. Verification & Quality Assurance Guarantee

Run full local test and lint suites to ensure 100% green CI/CD passing with zero regressions.
CI Guarantee: 100% green local test runs, zero linter/formatter warnings, and clean build checks before opening the PR.

4. Turnaround SLA & Track Record

Estimated Delivery: Complete, atomic, ready-to-merge PR within 1–2 hours of assignment.
Zero Maintainer Overhead: Fully autonomous execution—branch is ready, dependencies reproduced locally, and ready to push.
Review SLA: Active availability with sub-15 minute revisions for any requested review tweaks.
Verified Pedigree: 166+ Merged PRs across Stellar & Web3 protocols | OSS Activity Score: 83 (Top 2% Global Contributor) | Fast & deterministic protocol-grade delivery.

Looking forward to your green light! Ready to branch and ship.

@pre-cious-Igwealor

@pre-cious-Igwealor has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

can i work on this?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @pre-cious-Igwealor to this issue.

@kosisochukwu1234

@kosisochukwu1234 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

I can work on this task, allow me to work on it, thanks

ℹ️ Repo Maintainers: To accept this application, review their application or assign @kosisochukwu1234 to this issue.

@kosisochukwu1234

Congratulations, @kosisochukwu1234! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.

🧑‍💻 @kosisochukwu1234: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

Closed by #689, merged into dev.

Navigation Menu

Repository navigation

ADR: per-device envelopes instead of shared ciphertext #641

⚡ Protocol Implementation Blueprint & Production Readiness Proposal

1. Scope & Execution Boundary

2. Implementation Strategy & Invariants

3. Verification & Quality Assurance Guarantee

4. Turnaround SLA & Track Record

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

ADR: per-device envelopes instead of shared ciphertext #641

Description

Activity

maxx-GENIUS commented on Oct 20, 2026

maxx-GENIUS commented on Oct 20, 2026

⚡ Protocol Implementation Blueprint & Production Readiness Proposal

1. Scope & Execution Boundary

2. Implementation Strategy & Invariants

3. Verification & Quality Assurance Guarantee

4. Turnaround SLA & Track Record

pre-cious-Igwealor commented on Oct 20, 2026

kosisochukwu1234 commented on Oct 20, 2026

drips-wave commented on Oct 20, 2026

github-actions commented on Oct 28, 2026

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions