Add unit tests for protocol fee recipient update emitting correct event fields

[Chucks1093]

Summary

The ProtocolFeeRecipientUpdated event must contain both the old and new recipient addresses. A unit test should assert each field individually to confirm the event is emitted correctly after a successful update.

Scope

• Record the current protocol fee recipient as the old address
• Call update_protocol_fee_recipient with a new address
• Capture the emitted event and assert old_recipient matches the previous address
• Assert new_recipient matches the address passed to the update call

Acceptance Criteria

• old_recipient field matches address before the update
• new_recipient field matches the address passed in
• Event is emitted exactly once per update call

ETA: 12 hours

---

Coordinate on Telegram

[Zeemnew]

@Zeemnew has applied to work on this issue as part of the Stellar Wave Program's 6th 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 @Zeemnew to this issue.

[emteebug12-jpg]

@emteebug12-jpg has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I'm looking to make my first contributions to this project and would love to take a look at this issue.

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

[privexlabs]

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

Hi, I would like to work on this

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

[drips-wave]

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

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

[grantfox-oss]

🦊 GrantFox — @privexlabs has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

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

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@privexlabs's PR #493 was approved and merged by @Chucks1093.

🏆 @privexlabs: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (156 total points). Track your full progress on GrantFox.

👏 Great work, @privexlabs! Keep contributing to accesslayerorg.

[drips-wave]

This issue has been completed by @privexlabs as part of the Stellar Wave Program's 6th Wave 🥳

😎 @privexlabs: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.