Skip to content

ADR: Signal for direct messages, MLS for groups #642

Closed

Description

@codebestia

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

Description:
Write docs/adr/0002-signal-dms-mls-groups.md using the template from #320. Record why direct messages use X3DH plus the Double Ratchet while groups use MLS, and the transition plan from the Phase-1 sealed box.

Acceptance criteria:

  • Follows the ADR template
  • Covers the trade-offs that drove the split: per-device fan-out cost in large groups, MLS's lack of history for new members, and library and audit maturity
  • References the existing decision material (docs/signal-integration.md, apps/backend/docs/signal-migration.md) instead of restating it
  • Status reflects reality: which parts are live, which are implemented but not wired, and which are planned

Activity

  1. Tinu-ola commented on Oct 19, 2026

    @Tinu-ola

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

    Hi maintainer, please assign me to this issue.

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

  2. maxx-GENIUS commented on Oct 20, 2026

    @maxx-GENIUS

    ⚡ 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: Signal for direct messages, MLS for groups
    • Architectural Scope: Review codebase conventions, architectural structure, and requirements for ADR: Signal for direct messages, MLS for groups.

    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.

  3. pre-cious-Igwealor commented on Oct 20, 2026

    @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 issue?

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

  4. kosisochukwu1234 commented on Oct 20, 2026

    @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.

  5. drips-wave commented on Oct 20, 2026

    @drips-wave

    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 🌊

  6. github-actions commented on Oct 28, 2026

    @github-actions

    Closed by #690, merged into dev.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Stellar WaveIssues in the Stellar wave programdocumentationImprovements or additions to documentatione2ee

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions