Add deterministic event ordering tests for multi-operation transactions

[Jagadeeshftw]

Area: Events / indexer correctness · Estimated effort: 6–10 h

Problem

Event schema/versioning docs exist and many operations emit multiple events, but consumers need a guaranteed order when a batch changes several records.

Design decision required

Define event ordering as part of the ABI and decide whether failed operations emit compensating or no events.

Requirements

• Exercise batch, payout split, fee, and rollback paths
• assert topics/data/order and absence on failed transactions.

Acceptance criteria

• Event ordering is documented, golden fixtures cover multi-event transactions, and failure paths do not emit misleading success events.

Out of scope

• Unrelated refactors, dependency upgrades, or behavior changes outside the stated scope.
• Closing, deleting, or weakening existing tests to make the change pass.

Verification

cargo test --manifest-path contracts/bounty_escrow/Cargo.toml --workspace events -- --nocapture

PR requirements

• Explain the before/after behavior and include the evidence requested above.
• Add regression tests for the changed behavior and report relevant build, test, lint, and artifact results.
• Keep the PR focused and reference this issue.
• Please open the PR within 48 hours of assignment so the work remains active; ask a question in the issue if the scope needs clarification.

Good luck, and please join the contributor Telegram group if you want to discuss the work: https://t.me/+u5qmu35nZ7I0OTU1

[chidii]

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

Hello Maintainer, I've reviewed this issue thoroughly and I'm well positioned to resolve it — experienced across the relevant stack and comfortable navigating the existing codebase. Ready to start right away.

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

[Yerimahjr]

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

I’d like to work on this issue. I’ll define and document the event ordering contract for multi-operation transactions, then add deterministic golden fixtures covering batch, payout-split, fee, and rollback flows. The tests will verify event topics, data, and exact ordering, while failed transactions will be checked to ensure they emit no misleading success events. I’ll keep the changes focused on event/indexer correctness, add regression coverage without weakening existing tests, and run the specified workspace event tests plus relevant build and lint checks. The PR will include the before/after behavior and verification evidence requested.

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

[Moh-dakai]

@Moh-dakai has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi maintainer, I would like to work on this issue

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

[Lspnjr1]

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

I’ll love to work on this issue kindly assign boss

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

[Jagadeeshftw]

@Yerimahjr — Best of luck as you get started! You are now assigned to Add deterministic event ordering tests for multi-operation transactions (#1748). Your immediate focus is add deterministic event ordering tests for multi-operation transactions. Please read the complete issue description before starting, address every requirement and acceptance criterion in your PR, and raise a high-quality, focused implementation with the relevant tests and verification evidence. Keep the implementation scoped to the issue and make the verification evidence easy to find. Please open the PR within 48 hours of this assignment; if no PR is opened within that period, the issue may be unassigned so the work can be reassigned. You are also welcome to join our contributor Telegram group: https://t.me/+u5qmu35nZ7I0OTU1

[drips-wave]

Congratulations, @Yerimahjr! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @Yerimahjr: 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 🌊