Event schema: v2 symbols, `EVENT_SCHEMA_VERSION_V2`, indexer fixture golden vectors [RC26Q2-C12]

[thlpkee20-wq]

Description

Ensure the contract emits the intended v2 events for the audit/indexer story: include src/test_indexer_fixtures.rs (or similar) to lock payload shapes to golden expectations.

Requirements and context

• Breaking event fields must be versioned, not “silently” extended.

Suggested execution

• Fork the repo, then:

  • git checkout -b feature/soroban-events-v2-fixtures

• Relevant modules: src/lib.rs, src/test_indexer_fixtures.rs, docs/indexer-fixture-coverage.md

• Implement and verify

  • Extend events tests; document how indexers should branch on the version when multiple generations coexist in deployments.

• Test and document

  • Add or extend automated tests; cover edge cases and invariants
  • Document security assumptions; include test output summary and a short security / risk note in the PR
  • For Revora-Contracts (Soroban): cargo test, cargo clippy, rustdoc/NatSpec-style entrypoint docs where applicable. Do not implement Solidity; this work targets Rust/WASM in this repository.
  • For Backend / Frontend: follow the repo’s existing Jest/TS/ESLint/Vite setup.
  • Example commit message: test(soroban): v2 event and indexer golden fixtures

Labels and GitHub label colors

• Create the labels in this issue’s labels: line under Settings → Labels in the target repo.
• Assign distinct colors (avoid all grey): e.g. #0052CC (blue, platform), #B60205 (red, security), #0E8A16 (green, tests), #5319E7 (purple, P1), #F9D0C4 (scope), #1D76DB (api), #BFD4F2 (docs) — pick a non-default palette so issues are scannable in the board.

Guidelines

• Target ≥ 95% test coverage for new or materially changed code paths
• Clear, linked documentation in-repo
• Timeframe: 96 hours from assignment

[Jay1280]

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

Hi please can you assign me this task

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

[drips-wave]

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

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