Skip to content

Client crypto module map #624

Closed
Closed

Description

@codebestia

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

Description:
Write apps/web/docs/crypto-module-map.md: one table listing every crypto-related module in apps/web/src/lib/ and apps/web/src/lib/crypto/ with its status — live (on the message path today), stub, or implemented but not wired. Contributors currently cannot tell which of crypto.ts, session.ts, signalClient.ts, signalSession.ts, x3dh.ts, crypto/doubleRatchet.ts, crypto/ratchetSession.ts, crypto/messageCrypto.ts, sessionStore.ts, crypto/sessionStore.ts, cryptoStore.ts, and prekeyStore.ts actually runs.

Acceptance criteria:

  • Every module listed once with status, responsibility, and its callers
  • Documents the SessionCrypto switch in session.ts: defaultSession is Phase1SessionCrypto today, and what activating LibsignalSessionCrypto requires (link to docs/signal-integration.md, do not duplicate it)
  • Calls out the known duplication explicitly, e.g. the two sessionStore.ts files, and ratchetSession.ts rejecting out-of-order messages while doubleRatchet.ts supports them
  • Includes a diagram of the live send and receive paths only

Activity

  1. Luna-netty commented on Oct 19, 2026

    @Luna-netty

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

    Hi, I’d love to take on this issue! With my expertise in Rust, Stellar, and smart contract development, I can implement a clean and efficient solution.

    🚀 Why Me?
    Proven Blockchain Experience – Hands-on work with Stellar, Solidity, and Rust, building secure and optimized smart contracts.
    Open Source Contributor – Actively contributed to 50+ open-source projects, showcasing adaptability and collaboration.
    Efficient & Reliable – I deliver high-quality, production-ready solutions quickly, ensuring security and scalability.
    ⏱ Timeline
    I estimate completing this within 24 hours. Let me know if I can proceed!

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

  2. Depo-dev commented on Oct 20, 2026

    @Depo-dev
    Contributor

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

    Hello team.

    I’m Depodev, a software engineer with a strong background in building scalable systems and contributing to open-source projects. I’ve taken some time to go through the repository and understand the current implementation, and I’m clear on the issue, its context, and the expected outcome.

    I’d love to work on this and take ownership of the fix. I’m confident I can cleanly resolve it while keeping everything aligned with the existing codebase and ensuring all criteria are met. Would appreciate being assigned to this issue.

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

  3. drips-wave commented on Oct 20, 2026

    @drips-wave

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

    🧑‍💻 @Depo-dev: 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 🌊

  4. github-actions commented on Oct 20, 2026

    @github-actions

    Closed by #649, merged into dev.

  5. drips-wave commented on Oct 20, 2026

    @drips-wave

    This issue has been completed by @Depo-dev as part of the Stellar Wave Program's 10th Wave 🥳

    😎 @Depo-dev: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

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

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programdocumentationImprovements or additions to documentatione2eefrontend

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions