forge-multisig — add support for native XLM transfers not just Soroban token transfers

[Austinaminu2]

Summary

forge-multisig currently only supports token transfers via token::Client::new() which works for Soroban tokens (SAC-wrapped assets). It does not support native XLM transfers which use a different interface. Many Stellar treasuries hold native XLM and would not be able to use forge-multisig for XLM disbursements.

Proposed Design

Add a separate proposal type for native XLM transfers using Stellar's built-in transfer mechanism.

propose_xlm(env: Env, proposer: Address, to: Address, amount: i128) -> u64

Tasks

• Research the correct Soroban method for native XLM transfers
• Add is_native: bool field to Proposal to distinguish XLM from token proposals
• Implement propose_xlm() that creates a native XLM transfer proposal
• Update execute() to handle both token and native XLM cases
• Add tests for native XLM proposal creation, approval, and execution
• Document native XLM support in the contract README

Labels: enhancement, forge-multisig

[Just-Bamford]

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

Hi, I’d like to work on this issue.

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

[drips-wave]

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

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

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @Just-Bamford as part of the Stellar Wave Program's 4th Wave 🥳

Moderator's reason: [Auto-assessed] The contributor successfully implemented all requirements of the issue, including the propose_xlm function, the is_native flag for proposals, and comprehensive unit tests. The PR has been reviewed and merged by the repository maintainer, confirming the quality and relevance of the contribution.

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

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.