You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Write apps/backend/docs/concepts-nonce-lifecycle.md for lib/nonce.ts: how challenge nonces are minted, stored, consumed and expired, for both the sign-in challenge and the separate device-link challenge.
Acceptance criteria:
Documents creation, single-use consumption and TTL for both nonce kinds
Explains why device-linking uses a separate nonce namespace from sign-in, so hammering one flow cannot lock out the other
Documents where nonces live and the behaviour across a restart or in a multi-node deployment
Explains the replay resistance this provides and its limits
@BigManly4 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
I'd like to contribute to this issue. As a full-stack and backend developer with open-source experience, I'll provide a high-quality implementation and keep the discussion updated throughout the process.
Congratulations, @BigManly4! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.
🧑💻 @BigManly4: 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.
😎 @BigManly4: 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.
Activity
Davichi-1 commentedon Aug 30, 2026
@Davichi-1 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Davichi-1 to this issue.
BigManly4 commentedon Aug 30, 2026
@BigManly4 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @BigManly4 to this issue.
drips-wave commentedon Aug 30, 2026
Congratulations, @BigManly4! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.
🧑💻 @BigManly4: 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 🌊
github-actions commentedon Aug 31, 2026
Closed by #599, merged into
dev.drips-wave commentedon Aug 31, 2026
This issue has been completed by @BigManly4 as part of the Stellar Wave Program's 8th Wave 🥳
😎 @BigManly4: 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.