Add multi-asset support to revenue_split contract

[Wilfred007]

What

Revenue_split currently handles single-asset splits. Add support for splitting multiple assets in one transaction call.

Why

Organizations may need to split revenue in multiple currencies (USD, EUR, BTC) simultaneously. Currently requires separate calls per asset.

Scope

In scope: Accept vector of (asset, amount) pairs, distribute each according to split percentages
Out of scope: Cross-asset conversion

Acceptance Criteria

• Accept multiple assets in single distribution call
• Each asset distributed according to same split percentages
• Events emitted per asset
• Tests with 2+ assets

Technical Context

• contracts/revenue_split/src/lib.rs — single-asset distribution

[Queenode]

I’d like to work on adding multi-asset support to the revenue_split contract.

The current implementation handles a single asset per distribution call. I would extend this flow to accept multiple (asset, amount) pairs and distribute each asset using the existing split percentages, without introducing any cross-asset conversion logic.

Implementation Approach

I would first review the existing revenue_split contract, particularly the current single-asset distribution logic, storage structures, events, and tests, so the new functionality remains consistent with the existing design.

My implementation would:

• Extend the distribution interface to accept a vector of (asset, amount) pairs.
• Reuse the existing split percentage calculation for every asset.
• Process each asset independently within the same transaction.
• Emit the appropriate distribution event for each asset.
• Preserve the existing single-asset behavior where possible.
• Ensure invalid assets, amounts, or distribution conditions fail safely without leaving partial state changes.

Testing

I would add tests covering:

• Distribution of two or more assets in a single call.
• Correct percentage allocation for every asset.
• Event emission for each distributed asset.
• Multiple recipients receiving their expected share across all assets.
• Invalid input and failure cases.
• Regression tests to ensure existing single-asset distribution continues to work.

[grantfox-oss]

🦊 GrantFox — @Queenode has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #526)
2. Your PR will be reviewed by the Protocol-Guild maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!

@Queenode's PR #582 was approved and merged by @Wilfred007.

🏆 @Queenode: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (500 total points). Track your full progress on GrantFox.

👏 Great work, @Queenode! Keep contributing to Protocol-Guild.