Add replay-safety guard against fork-replays of report_revenue across networks

[thlpkee20-wq]

Description

A report_revenue signature replayed on a forked or sibling network could double-credit. Encode the network passphrase hash into the report payload and reject reports whose embedded network_id does not match the current network.

Requirements and context

• Must be secure, tested, and documented
• Should be efficient and easy to review
• Relevant code: Revora-Contracts/src/lib.rs
• Network-id check must run before any state read to fail fast and cheap

Suggested execution

• Fork the repo and create a branch
• git checkout -b feat/replay-safety-network-id
• Implement changes
  • Read env.ledger().network_id() and require payload.network_id == env_network_id
  • Reject with NetworkIdMismatch typed error
  • Add fixture exercising a known testnet payload replayed against a mocked mainnet env
• Validate security and correctness assumptions

Test and commit

• Run tests
  • cargo test --all
• Cover edge cases
  • Cross-passphrase forks must reject even when all other fields match
• Include test output and security notes

Example commit message

feat: bind report_revenue to network_id to block cross-fork replay

Guidelines

• Minimum 95 percent test coverage
• Clear documentation
• Timeframe: 96 hours

[grantfox-oss]

🦊 GrantFox — @Gbena-afk has been assigned to this issue!

Next steps:

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

Good luck! Track your progress on GrantFox.

[drips-wave]

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

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