Add regression test for transfer_keys not affecting sender or recipient dividend claimable balance

[Chucks1093]

Summary

A peer-to-peer key transfer should not alter either wallet's claimable dividend balance from a prior distribution. The transfer moves ownership but pending dividends stay with the wallet that held keys at distribution time.

Scope

• Distribute a dividend to a creator with two holders
• Record both wallets' claimable balances before transfer
• Transfer keys from wallet A to wallet B
• Assert wallet A's claimable balance is unchanged
• Assert wallet B's claimable balance is unchanged

Acceptance Criteria

• Sender claimable balance unchanged after transfer
• Recipient claimable balance unchanged after transfer
• Both wallets can still claim their pre-transfer dividend amounts

ETA: 12 hours

---

Coordinate on Telegram

[JudeDaniel6]

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

hello Maintainer, Please can i work on this issues and give you a better result

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

[EneGab]

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

I can work on this issue, please assign me

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

[Demilade10]

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

I would like to work on this issue

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

[ONEONUORA]

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

HI
I am a full stack developer with 5 years of experience building scalable apps
I believe i can handle this issue

ETA 6hrs

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

[grantfox-oss]

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

Good luck! Track your progress on GrantFox.

[drips-wave]

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

🧑‍💻 @ONEONUORA: 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]

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

@ONEONUORA's PR #495 was approved and merged by @Chucks1093.

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

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

[drips-wave]

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

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