Skip to content

Flow docs: linking a new device #637

Closed

Description

@codebestia

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

Description:
Write docs/flows/device-linking.md: adding a second device from start to finish — POST /devices/link/challenge and POST /devices/link/verify (each with its own rate limiter), prekey and MLS key-package upload from the new device, sibling-device fan-out picking it up, MLS Welcome for groups, and the devices page (app/app/devices/page.tsx) where the user manages and revokes devices.

Acceptance criteria:

  • A sequence diagram across the new device, an existing device, and the backend
  • States what history the new device can and cannot read — DMs versus MLS groups — linking to mls-group-membership.md for the group case
  • Documents the audit events recorded and the key-change notice other users see
  • Documents revocation as the reverse flow: what is deleted, which events are published, and what peers see

Activity

  1. TMTOFFUTA commented on Oct 19, 2026

    @TMTOFFUTA

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

    Hello Maintainer, I’ve reviewed the issue description and have a clear understanding of what is expected. I’d be happy to take the opportunity to work on it.

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

  2. omarima-10 commented on Oct 20, 2026

    @omarima-10

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

    I would like to work on this issue.

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

  3. drips-wave commented on Oct 20, 2026

    @drips-wave

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

    🧑‍💻 @omarima-10: 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 22, 2026

    @github-actions

    Closed by #682, merged into dev.

  5. drips-wave commented on Oct 22, 2026

    @drips-wave

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

    😎 @omarima-10: 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 documentatione2ee

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions