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
{{ message }}
Repository navigation
Build key curve update timelock indexer and pending proposals REST API #1113
Index CurveUpdateProposed and CurveUpdateExecuted contract events and expose REST endpoints for pending and completed bonding curve parameter update proposals per key.
Scope
Indexer processes both events into curve_updates table
GET /keys/:key_id/curve-updates/pending — returns pending proposals with eta and proposed params
GET /keys/:key_id/curve-updates/history — completed and cancelled updates with outcomes
ETA countdown computed at request time
Cache TTL 60s; invalidated on new curve update event for key
Acceptance Criteria
Both events indexed with no gaps
Pending endpoint returns accurate proposals with correct eta
ETA countdown computed correctly at time of request
History returns accurate completed and cancelled records
Cache invalidates correctly on new event for affected key
I analyzed "Build key curve update timelock indexer and pending proposals REST API" in accesslayerorg/accesslayer-server and have a concrete technical roadmap to resolve it.
I have reviewed the problem description and acceptance criteria for this issue. I have a clear, tested implementation ready with defensive error handling and 100% green CI proof.
I will deliver a clean, well-tested, and production-ready PR promptly upon assignment. Kindly assign this issue to me.
@Whiznificent has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
Hi Maintainer, I’d like to take this issue if it’s still available. I’ve reviewed the details and understand the expected changes. I can jump into it immediately and aim to get a working PR up within the next few hours.
⚡ Protocol Implementation Blueprint & Production Readiness Proposal
Hi @maintainers, I am ready to implement and ship this issue immediately.
I have reviewed the repository architecture and pre-analyzed the execution path for this task so you don't have to spend any time onboarding or hand-holding:
Congratulations, @nasarajoe! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @nasarajoe: 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.
😎 @nasarajoe: 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.
Activity
guptakumarranjeet150 commentedon Oct 19, 2026
Hi team,
I analyzed "Build key curve update timelock indexer and pending proposals REST API" in accesslayerorg/accesslayer-server and have a concrete technical roadmap to resolve it.
I have reviewed the problem description and acceptance criteria for this issue. I have a clear, tested implementation ready with defensive error handling and 100% green CI proof.
I will deliver a clean, well-tested, and production-ready PR promptly upon assignment. Kindly assign this issue to me.
Thank you!
Whiznificent commentedon Oct 19, 2026
@Whiznificent has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Whiznificent to this issue.
omoh5 commentedon Oct 19, 2026
@omoh5 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @omoh5 to this issue.
maxx-GENIUS commentedon Oct 19, 2026
@maxx-GENIUS has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @maxx-GENIUS to this issue.
maxx-GENIUS commentedon Oct 19, 2026
⚡ Protocol Implementation Blueprint & Production Readiness Proposal
Hi @maintainers, I am ready to implement and ship this issue immediately.
I have reviewed the repository architecture and pre-analyzed the execution path for this task so you don't have to spend any time onboarding or hand-holding:
1. Scope & Execution Boundary
Build key curve update timelock indexer and pending proposals REST APIBuild key curve update timelock indexer and pending proposals RES.2. Implementation Strategy & Invariants
3. Verification & Quality Assurance Guarantee
4. Turnaround SLA & Track Record
Looking forward to your green light! Ready to branch and ship.
deborahogunjinmi592-byte commentedon Oct 19, 2026
@deborahogunjinmi592-byte has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @deborahogunjinmi592-byte to this issue.
nasarajoe commentedon Oct 19, 2026
@nasarajoe has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @nasarajoe to this issue.
drips-wave commentedon Oct 19, 2026
Congratulations, @nasarajoe! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @nasarajoe: 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 commentedon Oct 20, 2026
🎉 This issue has been marked as completed on GrantFox!
@nasarajoe's PR #1126 was approved and merged by @Chucks1093.
🏆 @nasarajoe: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (471 total points). Track your full progress on GrantFox.
👏 Great work, @nasarajoe! Keep contributing to accesslayerorg.
drips-wave commentedon Oct 20, 2026
This issue has been completed by @nasarajoe as part of the Stellar Wave Program's 10th Wave 🥳
😎 @nasarajoe: 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.