[Testing] No idempotency test for the withdrawnAmount/topped-up financial fields when an event is re-processed

[grantfox-oss]

Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0

Why this matters

tests/soroban-event-worker.test.ts Event processing idempotency only covers stream_created, fee_collected, and replayed stream_paused/stream_resumed - all of which use upsert or set-absolute fields. There is no test that re-processes a tokens_withdrawn event and asserts handleTokensWithdrawn does not double-increment Stream.withdrawnAmount, nor a test confirming handleStreamToppedUp's depositedAmount stays correct under replay.

Acceptance criteria

• Add a test that runs handleTokensWithdrawn twice for the same txHash and asserts withdrawnAmount changes exactly once
• Add a test that replays stream_topped_up and asserts depositedAmount/endTime are not double-applied
• Wire these into the existing idempotency describe block

Files to touch

• backend/tests/soroban-event-worker.test.ts
• backend/src/workers/soroban-event-worker.ts

Out of scope

• Integration tests against a live RPC

[AugistineCreates]

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

I will solve this issue well and submit pr today

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

[BernardOnuh]

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

Hi maintainer, I would love to contribute to this issue by applying the necessary fixes and improvements to get it done

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

[Caneryy]

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

Hi maintainer, can I work on this issue?

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

[drips-wave]

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

🧑‍💻 @BernardOnuh: 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 — @BernardOnuh has been assigned to this issue!

Next steps:

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

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@BernardOnuh's PR #982 was approved and merged by @ogazboiz.

🏆 @BernardOnuh: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (611 total points). Track your full progress on GrantFox.

👏 Great work, @BernardOnuh! Keep contributing to LabsCrypt.