Repository navigation
Build alerts and dashboards for settlement latency, indexer lag, and reconciliation #281
Description
Activity
@Hayatt74 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
Hi I’d love to work on this issue
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Hayatt74 to this issue.
@orsar-rita has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
can i work on this issue please, thank you
ℹ️ Repo Maintainers: To accept this application, review their application or assign @orsar-rita to this issue.
Congratulations, @orsar-rita! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.
🧑💻 @orsar-rita: 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 🌊
- added a commit that references this issue
on Sep 29, 2026 This issue has been completed by @orsar-rita as part of the Stellar Wave Program's 9th Wave 🥳
😎 @orsar-rita: 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.
Objective
Deliver build alerts and dashboards for settlement latency, indexer lag, and reconciliation as a production-ready capability for QuickEx. This is an advanced issue: preserve self-custody, the documented API contracts, and the financial invariants while handling failure and rollback paths.
Scope
app/frontend,app/backend,app/mobile, andapp/contractas applicable.Acceptance criteria
Workstream
Notifications, webhooks, observability, and operationsReferences
Start with
docs/CAPABILITY-MAP.md,docs/BACKEND-CLIENT-CONTRACT-MAP.md, anddocs/INVARIANTS.md; use the owning module and neighboring tests as the implementation authority.Contributor notes
Before opening a PR, record assumptions about network, custody, and backward compatibility. Include test commands and any follow-up migration or rollout issue in the PR description.