Regression: wrong usdc_token parameter

[1nonlypiece]

Description

Must not move wrong asset.

Requirements and context

• Minimum 95% coverage on new test code paths

• Edge cases enumerated in PR

• Must be secure, fully tested, and documented

• Should be efficient and easy to review for auditors and integrators

Suggested execution

1. Fork the repository and create a branch: git checkout -b test/regression-wrong-token
2. Implement the changes listed below
3. Open a draft PR early for design feedback

Implement

• Add tests under tests/ or src/test.rs
• Document fixtures in TESTING_GUIDE.md if needed

Tests and documentation

• Add or extend automated tests: tests/create_vault.rs, src/test.rs
• Add or update documentation: TESTING_GUIDE.md, TEST_SUMMARY.md
• Add Rustdoc (///) on public contract APIs where applicable (NatSpec-style)
• Validate stated security assumptions explicitly in PR description

Test and commit

1. Run the full contract test suite (e.g. cargo test, Soroban local sandbox if applicable)
2. Cover edge cases called out in this issue
3. Attach test output summary and short security notes in the PR
4. Ensure minimum 95% line coverage for touched modules (cargo tarpaulin / project standard)

Example commit message

test(soroban): regression wrong token

Guidelines

Item	Target
Test coverage	≥ 95% on changed code
Documentation	Clear, versioned, matches on-chain behavior
Timeframe	96 hours from assignment

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[drips-wave]

@1nonlypiece shoaib050326 could not be assigned to this issue because they have reached the maximum of 4 accepted assignments per organization in the current wave of the Stellar Wave Program.

The assignee has been removed. Please choose a different contributor.

[drips-wave]

@1nonlypiece shoaib050326 could not be assigned to this issue because they have reached the maximum of 4 accepted assignments per organization in the current wave of the Stellar Wave Program.

The assignee has been removed. Please choose a different contributor.

[drips-wave]

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

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