[Backend] Pause/resume controllers persist placeholder-txHash PAUSED/RESUMED events that the indexer re-writes - duplicate history rows

[grantfox-oss]

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

Why this matters

stream.controller.ts:641-650 (pause) and :740-752 (resume) write a StreamEvent with transactionHash = result.txHash, which sorobanService returns as the fabricated simulated-pause- / simulated-resume- and ledgerSequence:0. When the genuine on-chain event is later indexed, the worker inserts a SECOND StreamEvent keyed on the real txHash. Because @@unique is (transactionHash, eventType) and the two txHashes differ, both rows survive -> duplicate PAUSED/RESUMED entries with a bogus ledgerSequence 0.

Acceptance criteria

• Stop writing a synthetic-txHash StreamEvent in the pause/resume controllers, or reconcile/replace it when the real indexed event arrives
• Ensure pause/resume state is written by exactly one source
• Add a test that pauses then indexes the real stream_paused event and asserts a single PAUSED row

Files to touch

• backend/src/controllers/stream.controller.ts
• backend/src/services/sorobanService.ts
• backend/src/workers/soroban-event-worker.ts

Out of scope

• Real frontend-signed transaction submission flow

[Kayce10]

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

Please assign this issue to me my eta is 4 hours

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

[elcabasa]

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

Hi team,

I would love to take on this issue! Eliminating the duplicate rows caused by the placeholder transaction hashes is highly important for keeping the stream history ledger accurate and preventing inconsistencies between simulated states and genuine on-chain indexing.

I am ready to refactor the pipeline across the specified files to meet all acceptance criteria:

• Controller Refactoring: Remove the generation of the synthetic-txHash StreamEvent inside the pause and resume controllers (stream.controller.ts), ensuring that historical event logs are driven exclusively by a single source of truth.
• State Reconciliation: Align sorobanService.ts and soroban-event-worker.ts so that PAUSED and RESUMED event entries are written cleanly only when the authentic, indexed on-chain event arrives.
• Integration Testing: Add a test case that triggers a stream pause, simulates the arrival of the genuine indexed stream_paused event, and asserts that exactly one deterministic PAUSED row remains in the database.

I will ensure my changes are strictly focused on the backend event synchronization and keep frontend transaction submission logic completely out of scope. Could you please assign this issue to me? I'll head over to the Telegram group to claim it as well. Thanks!

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

[Caneryy]

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

Hello, I'd like to work on this issue.

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

[Banx17]

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

Please assign this issue to me.

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

[drips-wave]

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

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

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #804)
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!

@Banx17's PR #981 was approved and merged by @ogazboiz.

🏆 @Banx17: You earned 35 FoxPoints for this contribution! Your current tier: Builder (1,021 total points). Track your full progress on GrantFox.

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