Multi-Recipient Payment Splitter Contract

[Mkalbani]

Location: contracts/payment_splitter
Estimated Time: 6 hours

Description

A generalised payment splitting contract that receives token deposits and automatically distributes them to a configured list of recipients according to predefined share percentages. Useful for splitting platform fees, puzzle creator royalties, or guild treasury payouts among multiple parties.

Tasks

• Design SplitConfig struct: id, recipients: Vec<(Address, BasisPoints)>, token, total_released
• recipients share weights must sum to 10000 bps; validated on config creation
• Implement create_split(recipients, token) — registers a new split configuration
• Implement deposit(split_id, amount) — anyone can deposit; funds accumulate in contract
• Implement release(split_id) — distributes current balance to all recipients per their share
• Implement release_to(split_id, recipient) — releases only one recipient's accumulated share
• get_split(split_id) — returns config, total deposited, total released, per-recipient released amounts
• Admin function to update recipient list (only before first deposit)
• Emit Deposited(split_id, amount), Released(split_id, recipient, amount) events
• Write tests: create, deposit, release all, release one, share validation, post-deposit config lock

Acceptance Criteria

• Shares validated to sum to 100% on creation
• Deposits accumulate correctly
• Release distributes exact proportional amounts
• Config locked after first deposit
• Contract deployed to testnet

[rohan911438]

@rohan911438 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hi, I’d like to take this up. I understand the requirements and approach, and I’m ready to start immediately. I’ll deliver a clean, well-tested solution with a quick turnaround. Kindly assign this to me.

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

[Codekill33]

@Codekill33 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hello, i'd like to work on this as it aligns with my expertise. i can implement this feature.
I have solid experience with smart contracts.
Kindly assign me to this issue. ETA 6 hours

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

[drips-wave]

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

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