Fix Race Condition in On-Chain Event Ingestion Sequence

[AlAfiz]

Description: The event ingestion worker occasionally processes Stellar ledgers out of chronological order under heavy network load, leading to race conditions where a Swap event is recorded before the corresponding pool's Mint or initialization event.
Context / Motivation: Out-of-order event ingestion corrupts historical balance tracking and displays inaccurate TVL metrics on the client dashboard. We must guarantee strict sequential processing based on ledger sequence numbers.
Acceptance Criteria:

• Implement a concurrency lock or sequential queue mechanism (e.g., using a mutex or a job queue like BullMQ) to ensure ledger $N$ is fully processed before ledger $N+1$ begins execution.
• Add a database constraint to prevent duplicate ingestion of the same ledger sequence.
• Write integration tests simulating rapid block emissions to verify sequential database writes.
  Technical Pointers: Review the ingestion polling loop. Instead of triggering unawaited async mapping loops over an array of blocks, resolve them sequentially using a strict for...of loop or an ordered transaction pipeline.

[demonchant]

I reviewed the ingestion worker and noticed that while event processing itself is sequential, overlapping polling cycles can still occur because the polling loop is driven by setInterval. I'd like to introduce a locking/queue mechanism to guarantee that a ledger batch is fully processed before the next batch begins, add duplicate-ingestion protection at the database layer, and verify ordering through integration tests.

[gloskull]

Hi, I would love to work on this Issue.
I have 4 years of experience delivering solutions for projects like this, covering backend, frontend, full-stack and smart contract development. After carefully reviewing your requirements, I have a clear understanding of the task and am confident in my ability to deliver a clean, efficient, and thoroughly tested solution on time. I prioritize code quality, maintainability, and industry best practices throughout the development process.
My PR will be submitted in under 10hours.

[Truphile]

Hi team, I’d love to take this on!

As a returning contributor, I’m already familiar with the repository workflow and setup. This is right up my field I’ve implemented very similar architectural patterns and requirements before.

I’ve reviewed the acceptance criteria and can deliver a clean, well-tested solution immediately. Ready for assignment!

[benedict-cmd]

I'm a developer please assign me to this issue and I promise to deliver as expected

[alexitsejames-cpu]

I am a developer please assign me to this issue and I will deliver Morethan expected

[guptakumarranjeet150]

Hello @maintainers,

I can tackle Fix Race Condition in On-Chain Event Ingestion Sequence. Proposed implementation roadmap:

• Analysis: Inspect current behavior and edge cases in BETAIL-BOYS/TradeFlow-API
• Core Implementation: Implement backend logic for Fix Race Condition in On-Chain Event Ingestion Sequence with strict schema validation and idempotent execution.
• Quality Assurance: Add integration test suites for standard invocations and boundary/error conditions.

I can start working on this right away. Please assign!