Add regression test for creator fee recipient receiving correct amount on buy after rotation

[Chucks1093]

Summary

After a creator rotates their fee recipient address, the new address must receive the creator fee on subsequent trades. The old address must receive nothing. A regression test should confirm the fee routing updates correctly after the rotation.

Scope

• Register a creator and record the initial fee recipient
• Execute a buy and confirm the initial recipient received the fee
• Rotate the creator fee recipient to a new address
• Execute another buy and confirm the new recipient received the fee
• Assert the old recipient balance did not increase on the second buy

Acceptance Criteria

• Initial recipient receives fee before rotation
• New recipient receives fee after rotation
• Old recipient receives nothing after rotation

ETA: 12 hours

---

Coordinate on Telegram

[Chinonso-Peter]

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

Can i work on this issue

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

[Ademiitura]

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

Kindly assign
Thanks

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

[Achievers-sketch]

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

Experienced Rust and Soroban developer. I’ll add comprehensive regression tests validating creator fee recipient

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

[Oluwasuyi-Timilehin]

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

Hello, I’m a full stack developer with hands-on experience building with variety of tools including Nextjs, nodejs, nestjs, React, Typescript and more
I focus on writing clear, maintainable code and making sure features work as expected end to end, not just in isolation. I communicate progress regularly and keep things transparent as I work. I’m confident I can complete this task within an ETA of 4 HOURS

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

[Alaka-ibr]

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

Hi maintainer, will love to work on this.

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

[wheval]

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

Hello i would love to work on this.

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

[drips-wave]

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

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

Good luck! Track your progress on GrantFox.