Implement Soroban event indexer to sync on-chain events to database

[ogazboiz]

Join our community: https://t.me/+DOylgFv1jyJlNzM0

Description

The soroban-event-worker.ts file exists but the actual indexing logic is not implemented. The database schema (StreamEvent, IndexerState) is ready, but no on-chain events (CREATED, TOPPED_UP, WITHDRAWN, CANCELLED, COMPLETED) are being written to it. The entire API relies on indexed data — this is the most critical missing piece.

What Needs to Happen

• Connect to Stellar RPC and poll for contract events every 5 seconds (configurable via POLL_INTERVAL_MS)
• Cursor-based pagination using IndexerState.lastProcessedLedger
• Parse and map each event type to a StreamEvent DB record
• Deduplicate events by transactionHash + eventType + ledger to handle restarts safely
• Update Stream state in DB on each relevant event (amounts, status)
• Emit SSE broadcast after each successful event batch

Files

• backend/src/workers/soroban-event-worker.ts
• backend/src/services/indexerService.ts (create)

Acceptance Criteria

• Events appear in DB within 10 seconds of on-chain confirmation
• Indexer survives restarts without missing or duplicating events
• All 5 event types mapped correctly

[2411015047-afk]

Hi @ogazboiz! I can help implement the Soroban event indexer to sync on-chain events to your database.

I have experience building:

• Event indexing pipelines for Soroban contracts (listening for CREATED, TOPPED_UP, WITHDRAWN, CANCELLED, COMPLETED events)
• Database schema design with StreamEvent and IndexerState models
• RPC subscription patterns for efficient ledger sync

This can be delivered as a standalone worker script or integrated with your existing .

Would you like to hire this out? I can discuss timeline and approach in detail.

[2411015047-afk]

Hi! I can implement the Soroban event indexer for you. I have hands-on experience with:

• Connecting to Stellar RPC and polling for contract events
• TypeScript/Node.js event parsing (CREATED, TOPPED_UP, WITHDRAWN, CANCELLED, COMPLETED)
• Database writes with proper error handling and retry logic

This is a well-scoped task — happy to discuss timeline and budget. Let me know if you'd like to move forward.

[shakurJJ]

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

I would like to work on this issue

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

[drips-wave]

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

🧑‍💻 @shakurJJ: 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 @shakurJJ as part of the Stellar Wave Program's 4th Wave 🥳

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