Standardize SafeERC20 usage for non-compliant tokens

[Baskarayelu]

Standardize SafeERC20 usage for non-compliant tokens

Description

• Direct transfer/transferFrom calls can fail silently on non-standard tokens.

Requirements and context

• Cover all token movement paths.
• Preserve existing allowance and approval logic where possible.

Suggested execution

• Replace direct ERC20 calls with SafeERC20 wrappers.
• Handle safeIncreaseAllowance/forceApprove patterns as needed.

Test and commit

• Add tests using mock token without boolean return values.
• Validate failures revert consistently.

Example commit message

• refactor(contracts): migrate token flows to SafeERC20

Guidelines

• Avoid unsafe blanket approvals.
• Keep token address validation in place.

[tabithaglitch]

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

Hi maintainer, Good day, please can i work on this project. I have prior knowledge working on web3 issues and this wouldn't be a new thread for me. ETA 1HR.

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

[drips-wave]

Congratulations, @tabithaglitch! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

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