Create Event Processing Queue

[Abd-Standard]

Description

Introduce a queue system to process blockchain events asynchronously.

Tasks
Build a queue abstraction.
Prevent duplicate event processing.
Process events in order.
Handle retries.

Acceptance Criteria
Events are queued before processing.
Duplicate processing is prevented.
Failed jobs can be retried.

[Ved-viraj]

Hi can i be assigned this issue please? I've gone through the description and I'm up for the task. Kindly assign me please.

[N-thnI]

Dear maintainer
Please assign me this issue

[grantfox-oss]

🦊 GrantFox — @N-thnI has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

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

Good luck! Track your progress on GrantFox.

[bakarezainab]

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

Hi Maintainer, I am a web3 fullstack developer. I’ve reviewed this issue and I understand the requirements. I’d like to implement this and submit a clean PR. Kindly assign this issue to me. To prevent duplicate event processing, I will implement idempotency keys using a Redis cache with TTL that stores processed event signatures (block number + transaction hash + log index) and checks against this cache before enqueueing, ensuring each unique event is processed exactly once even during replay scenarios. For order preservation, I will use a single ordered queue or partition by event source with FIFO semantics, ensuring events from the same contract/stream are processed in the order they occur

I will implement retry logic with exponential backoff (e.g., 5 retries with delays: 1s, 5s, 15s, 60s, 5min) and dead-letter queues for failed jobs, with configurable retry limits and monitoring hooks for alerting on persistent failures. My implementation will include comprehensive tests for duplicate prevention (submitting the same event twice), order preservation (processing events out of sequence), retry mechanics (simulating failures and verifying retry behavior), and graceful shutdown handling. I am ready to deliver this queue system within 3-4 hours with full TypeScript types, detailed documentation, and integration with the existing Notify-Chain architecture

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

[CollinsC1O]

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

I would love to work on this issue and provide implementations to fulfill it.

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

[drips-wave]

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

🧑‍💻 @CollinsC1O: 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 — @CollinsC1O has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

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

Good luck! Track your progress on GrantFox.