Version the event payload format

[arisu6804]

Summary

Version the event payload format.

Context

Tracking issue for the RemitFlow smart contract. Open to contributors.

Acceptance criteria

• Implement the change described above
• Add or update automated tests
• Update the relevant documentation

[funds0033-cmyk]

Hi! I'd like to work on this issue.

Since the description is fairly high-level, my assumption is this covers adding a version field (or similar versioning scheme) to the contract's emitted events, so downstream consumers (indexers, the API layer) can handle payload changes without breaking as the schema evolves.

Approach:

Add a version identifier to each emitted event's payload.
Update or add tests confirming events emit with the correct version and that any existing consumers still parse them correctly.
Update docs/README covering the new event schema.

Happy to adjust scope once assigned if there's a specific event or migration path in mind — let me know if I'm off base on the interpretation, or if there's more context to share before I start.

[arisu6804]

This is yours, @funds0033-cmyk ✅ Two of you wanted it — you had fewer open items, so it's yours. Versioning the event payload is worth doing carefully. https://t.me/+8DgYV9HrNaA1Yjg1