Skip to content

Replay protection and event idempotency #558

Closed
Closed
Replay protection and event idempotency#558
Assignees
AdaBliss
Labels
Stellar WaveIssues in the Stellar wave programbackenddocumentationImprovements or additions to documentationsecurity

Description

@codebestia
codebestia
opened on Aug 27, 2026

Write apps/backend/docs/concepts-replay-protection.md covering services/replay-protection.service.ts and the dispatcher's idempotency path: how an eventId is recorded, the device-scoped key, the configurable TTL, and the dispatch_ack carrying duplicate: true/false.

Acceptance criteria:

  • Explains the two distinct layers — transport-level eventId dedup and message-level messageId idempotency — and why both exist
  • Documents that the dedup key is device-scoped, so one device's replayed id cannot block another device's legitimate event
  • Documents the TTL, that it is env-configurable, and the fail-open behaviour when Redis is unavailable
  • Notes that handlers are reachable only through the enveloped dispatch path, so every event gets this check

Activity

  1. codebestia
    added
    documentationImprovements or additions to documentation
    backend
    security
    on Aug 27, 2026
  2. drips-wave
    added
    Stellar WaveIssues in the Stellar wave program
    on Aug 27, 2026

  3. Wiseman52 commented on Aug 30, 2026

    @Wiseman52
    Wiseman52
    on Aug 30, 2026 – with Drips Wave

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

    Hi, kindly assign task. I’m confident I can take ownership of this task and deliver a well-tested solution that meets your expectations.

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

  4. Emmanuel945 commented on Aug 30, 2026

    @Emmanuel945
    Emmanuel945
    on Aug 30, 2026 – with Drips Wave

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

    Allow me fix it pls

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

  5. Emmanuelops commented on Aug 30, 2026

    @Emmanuelops
    Emmanuelops
    on Aug 30, 2026 – with Drips Wave

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

    Hi Maintainer! I’d love to take on this issue and get it done efficiently. Kindly assign it to me.

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

  6. AdaBliss commented on Aug 30, 2026

    @AdaBliss
    AdaBliss
    on Aug 30, 2026 – with Drips Wave

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

    I’d like to take this issue on. I’ll review the current implementation and relevant project guidelines first, then implement a maintainable solution with tests covering the expected behavior and edge cases

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

  7. drips-wave commented on Aug 30, 2026

    @drips-wave
    drips-waveBot
    on Aug 30, 2026 – with Drips Wave

    Congratulations, @AdaBliss! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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

  8. codebestia
    assigned
    AdaBliss
    on Aug 30, 2026
  9. codebestia
    added a commit that references this issue on Aug 31, 2026

    docs(backend): add protocol negotiation, replay protection, caching, …

    dc79047

  10. github-actions commented on Aug 31, 2026

    @github-actions
    github-actionsBot
    on Aug 31, 2026 – with GitHub Actions

    Closed by #600, merged into dev.

  11. github-actions
    closed this as completedon Aug 31, 2026

  12. drips-wave commented on Aug 31, 2026

    @drips-wave
    drips-waveBot
    on Aug 31, 2026 – with Drips Wave

    This issue has been completed by @AdaBliss as part of the Stellar Wave Program's 8th Wave 🥳

    😎 @AdaBliss: You earned 200 Points for completing this issue! After the current Wave ends, 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 programbackenddocumentationImprovements or additions to documentationsecurity

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions