Add unit tests for update_creator_fee_recipient rejected when called by non-current recipient

[Chucks1093]

Summary

Only the current fee recipient for a creator can rotate it to a new address. A call from any other wallet — including the creator's registered wallet — must be rejected with Unauthorized. This access control case needs explicit unit test coverage.

Scope

• Register a creator with a specific fee recipient address
• Attempt to call update_creator_fee_recipient from the creator's own wallet (not the fee recipient) and assert it reverts with Unauthorized
• Attempt from a random third wallet and assert it also reverts
• Call from the actual current fee recipient and assert it succeeds

Acceptance Criteria

• Call from creator wallet (not fee recipient) reverts with Unauthorized
• Call from random third wallet reverts with Unauthorized
• Call from current fee recipient succeeds and updates the address

ETA: 12 hours

---

Coordinate on Telegram

[akinboyewaSamson]

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

Hi! I’m a full-stack developer with a strong blockchain background. I’d love to handle this issue and can deliver a clean, reliable solution. Kindly assign it to me.

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

[MaimunaY]

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

Hi Maintainer, I am a SWE, and I've reviewed the requirements of Issue #501 and have a clean, efficient fix ready to go. With your permission I'd be glad to resolve this issue. Thank you.

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

[Akanimoh12]

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

Hi, I'd love to work on this issue. I'm a full-stack blockchain developer specializing in web apps and Smart Contracts, with experience in Next.js, TypeScript, Tailwind, and blockchain integration's and writing tests. I can handle this confidently, here's my portfolio and key projects:

• https://frontend-nine-mocha.vercel.app/
• https://i-predict.vercel.app/
• https://somnia-screams.vercel.app/
• https://chessflip-celo.vercel.app/

Active OSS contributor.

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

[drips-wave]

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

🧑‍💻 @Akanimoh12: 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 — @Akanimoh12 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 #501)
2. Your PR will be reviewed by the accesslayerorg maintainers

Good luck! Track your progress on GrantFox.

[BWM0223]

PR #506 submitted — fee recipient auth tests. Payment wallets ready: ETH 0xeaCAb48a4bfA0CED0e668c166615927115655594 | SOL C3MD2yfWYebB8FYXpq6ooqzU5GCQB1bDxbDhQf1JfiCW | BTC bc1qtmlgtvg7xgv0zry3ct90elp3y7d3ffdutk4e2f

[drips-wave]

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

😎 @Akanimoh12: 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.