tests(pool): verify existing LP balances are already valid under the new SEP-41 balance() with no migration needed

[K1NGD4VID]

Summary

Since the SEP-41 balance()/total_supply() functions (per the design doc) read the exact same DataKey::LPShares/DataKey::TotalShares storage that deposit()/withdraw() already populate, existing depositors' balances should already be valid under the new interface with no data migration script needed. This needs to be verified with a test, not assumed, since an incorrect assumption here would mean existing testnet LPs silently lose access to their position.

Acceptance Criteria

• Test added to contracts/pool/src/test.rs that deposits via the pre-SEP-41 deposit() path, then reads the resulting balance via the new balance() function and confirms they match exactly, with no migration step run in between
• If a gap is found (balances don't already line up), document the specific mismatch and scope a real migration issue instead of silently working around it
• Test added/updated and passing (cargo test)

Tech Stack

Rust, Soroban SDK, contracts/pool/src/test.rs, contracts/pool/src/lib.rs

[Olarewaju458]

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

Hi Maintainer, I’ve reviewed the issue carefully and understand what needs to be done. I’m interested in taking this task and can work on a clean implementation that follows the requirements and acceptance criteria. I’d appreciate the opportunity to contribute.

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

[GhazaL0113]

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

Hi Maintainer, I’ve reviewed this issue and understand the requirements. I’d like to take this issue and work on a clean solution that meets the acceptance criteria.

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

[Purity-Euphemia]

@Purity-Euphemia has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Please I can work on this 🙏😭Thank you

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

[Kaybee973]

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

I’m interested in working on this issue and have experience fixing similar problems. I’d be happy to contribute.

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

[drips-wave]

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

🧑‍💻 @Kaybee973: 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 🌊