Add admin function to rotate the protocol fee recipient address

[Chucks1093]

Summary

The protocol fee recipient address is set once at initialization and currently has no way to be updated. In practice teams rotate treasury addresses for security, move to multisig wallets, or migrate to a new setup. Without an update path, the only option is to abandon and redeploy the contract. An admin-only function to rotate the fee recipient solves this safely with a clear audit trail via event emission.

Scope

• Add update_protocol_fee_recipient(new_recipient: Address) function
  • Only callable by the current protocol admin address
  • new_recipient must not be the zero address
  • Updates the stored fee recipient in protocol config
  • Emits a ProtocolFeeRecipientUpdated { old_recipient, new_recipient } event
• Add corresponding update for creator fee recipient: update_creator_fee_recipient(creator_id, new_recipient: Address)
  • Only callable by the current fee recipient for that creator (self-rotation)
  • Emits CreatorFeeRecipientUpdated { creator_id, old_recipient, new_recipient }

Acceptance Criteria

• Protocol admin can update the fee recipient; new address receives fees on subsequent trades
• Non-admin call to update_protocol_fee_recipient is rejected with Unauthorized
• Zero address is rejected
• ProtocolFeeRecipientUpdated event emitted with correct old and new addresses
• Creator can rotate their own fee recipient; new address receives creator fees on next trade
• Non-current-recipient call to update_creator_fee_recipient is rejected
• Unit tests cover: successful rotation, unauthorized caller, zero address rejection, fee routing after rotation

---

Coordinate on Telegram

[OZILSOLAR]

Hi team!!!!
I would like to work on this issue!!!!!

[shadrach68]

I would like to work on this issue because I am a full-stack developer with 5+ years experience. I focus on identifying root causes and delivering clean, efficient, and maintainable solutions, with thorough testing to ensure reliable results.

[Divineifed1]

hi maintainer, kindly assign me this task so i can implement it as i have fully reviewed and understood

[JamesVictor-O]

Hello! I’d love to take on this issue. I’ve reviewed the requirements and have a clear path forward for the implementation. I estimate I can have a PR ready within about 3 hours of being assigned. Could you please assign this to me?

[barry01-hash]

I would love to work on this project

[grantfox-oss]

🦊 GrantFox — @JamesVictor-O 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 #395)
2. Your PR will be reviewed by the accesslayerorg maintainers

Good luck! Track your progress on GrantFox.