Emit distinct events for all ReceiptAnchor state changes

[wagmiiii]

Repo context. accensa-contracts holds the on-chain half of Accensa: ReceiptAnchor (Merkle batch anchoring) and RefundVault (policy-bounded refunds). Both are deployed on testnet and covered by unit tests. soroban-sdk 27.0.4, MIT. See README.md, docs/SECURITY_MODEL.md and DEPLOYMENTS.md before starting.

🟢 Unblocked. Event emission is non-blocking and additive to existing functions.

Problem

Off-chain services tracking ReceiptAnchor have difficulty reconstructing state because not all state changes (like admin updates or configuration changes) emit corresponding Soroban events.

What to build

1. Identify all state-mutating functions in ReceiptAnchor missing events.
2. Define structured event topics and data payloads.
3. Implement env.events().publish() for these state changes.

Acceptance criteria

• Events are emitted for all state changes.
• Event payloads contain necessary contextual data.
• Tests assert that events are published correctly.

Contact & Support

• Telegram
• Discord
• SUPPORT.md — contribution help, Wave process, and the full list of channels

[oyebolarotimi269-ai]

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

please assign this issue to me

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

[drips-wave]

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

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

[Oluwasuyi-Oluwatimilehin-Daniel]

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

Hello @maintainer, I’d like to work on this issue. I have experience handling similar tasks and can start immediately. And I will deliver at the shortest possible time.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Oluwasuyi-Oluwatimilehin-Daniel to this issue.

[felladaniel36-hash]

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

let me work on this

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

[drips-wave]

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

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