[Docs] backend/SSE_README.md is stale: marks shipped auth/per-IP/Redis as TODO and uses deprecated endpoints

[grantfox-oss]

Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0

Why this matters

SSE_README.md:103-110 lists Add JWT authentication, Implement per-IP connection limits and Add Redis pub/sub as unchecked TODOs, but all three are implemented. The curl/endpoint examples use the deprecated unversioned /events/subscribe and POST /streams, which now return 410 and require auth.

Acceptance criteria

• Check off the implemented production-considerations items and point remaining ones to their code
• Update examples to /v1/events/subscribe and the authenticated v1 stream endpoints
• Note that /events/subscribe now requires a JWT and returns 410 unversioned

Files to touch

• backend/SSE_README.md

Out of scope

• Rewriting docs/SSE_ARCHITECTURE.md

[olufunsoolutayo]

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

Hello Maintainer. I would love to resolve this issue. Please assign to me. Thank you

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

[femiolutayo]

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

Hello Maintainer. I would love to resolve this issue for you in no time. Please assign to me 🙏🏾😭. Thank you

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

[Osifowora]

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

​Hi maintainer, I would love to work on this issue. I can get started on it right away.

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

[Rampop01]

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

I would like to work on this issue . I understand the assignment and the requirements, and I’m confident in the approach needed to deliver the best solution. Kindly assign this task to me.

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

[dubemoyibe-star]

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

Can I work on this issue

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

[drips-wave]

Congratulations, @Rampop01! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

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

[grantfox-oss]

🦊 GrantFox — @Rampop01 has been assigned to this issue!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #848)
2. Your PR will be reviewed by the LabsCrypt maintainers

Good luck! Track your progress on GrantFox.