"[Enhancement] Implement Dead-Letter Queue for Events" labels: [enhancement, reliability, event-processing]

[robertocarlous]

Summary

Introduce a dead-letter queue (DLQ) mechanism to store unparseable or failed events. Include retry logic and manual intervention capabilities to ensure no events are lost.

Acceptance Criteria

• Unparseable events are stored in a DLQ
• Retry mechanism for failed events
• Manual intervention possible for DLQ events
• Monitoring and alerting for DLQ size
• Documentation updated

[Kaycee276]

Hi, I'd like to take this on! I'll implement a DLQ that captures unparseable and failed events, wire in configurable retry logic with backoff, expose a manual intervention interface for inspecting and reprocessing DLQ entries, add monitoring and alerting on DLQ size, and update the documentation throughout. PR in under 30 hours!

[supreme2580]

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

Hi can I be assigned to this issue?

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

[MethelyDev]

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

kindly assign this to me

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

[jaynomyaro]

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

Hi! I’m Jaynom, a full-stack developer with a background in blockchain. I would love to take on this issue. I have extensive experience in both frontend and backend development and am confident I can implement a clean solution. Could you please assign this to me?

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

[0xElyte]

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

I would like to resolve this fast 💯

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

[drips-wave]

Congratulations, @MethelyDev! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

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

[drips-wave]

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

😎 @MethelyDev: 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.