vesting revoke returns unvested tokens to current admin, not original funder

[ritaifeoluwa]

Description

The vesting wallet's revoke function transfers unvested tokens back to admin. However, if the admin address has changed via transfer_admin before revocation, the tokens go to the new admin, not the original admin who funded the vesting.

Current behavior

let admin = get_admin(&env);
admin.require_auth();
// ...
token::TokenClient::new(&env, &get_token(&env)).transfer(
    &env.current_contract_address(),
    &admin,  // This is the current admin, not the original funder
    &unvested,
);

Expected behavior

Consider storing the original funder address separately and returning unvested tokens to them on revocation.

Why this matters

The original funder may expect their tokens back, not the new admin. This could be a legal/compliance issue.

Labels

correctness, hard

[Emond-rgb]

@Emond-rgb has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello Team,
​I’d love to work on this issue. Given my background in backend development and framework architecture, I can take ownership of the fix.
​Let me know if you'd like me to share a quick proposal or draft a PR right away.
​Best regards,

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

[SupremeCarMart100]

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

Hi Maintainer,
I’d really appreciate the opportunity to work on this issue. Having reviewed the acceptance criteria, I’m confident that I can submit a PR after being assigned.
Please kindly assign this issue to me.
Thank you!

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

[0xSlink]

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

Hello maintainer, i would love to work on this issue

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

[drips-wave]

Congratulations, @0xSlink! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @0xSlink: 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 Third Campaign campaign!

@0xSlink's PR #210 was approved and merged by @ritaifeoluwa.

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

👏 Great work, @0xSlink! Keep contributing to SmartDropLabs.

[drips-wave]

This issue has been completed by @0xSlink as part of the Stellar Wave Program's 8th Wave 🥳

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