Implement Per-Offering Service Fee Wallets and Split Payouts

[thlpkee20-wq]

Description
Enable configuration of one or more service fee wallets per offering so that a portion of revenue is routed to platform or partner accounts before holder distributions.

Requirements and context

• Must allow specifying one or more fee recipients and their share (e.g., percentage or fixed bps).
• Must integrate with revenue distribution math so that only the net amount after service fees is used for token-holder distributions.
• Must emit events that describe the fee allocations for each distribution run.

Suggested execution

• Branch: git checkout -b feature/offering-service-fee-wallets.
• Extend offering configuration with a list/map of fee recipients and shares.
• Update distribution or claim logic to allocate amounts to service wallets first, then distribute remaining to holders.
• Add tests in src/test.rs with multiple fee recipients and verify sums and invariants.

Test and commit

• Run cargo test.
• Cover edge cases: no service fees, one recipient with 100%, multiple recipients summing to maximum allowed share.
• Include test output and notes on how off-chain indexers should read and display fee flows.

Example commit message
feat(contracts): add per-offering service fee wallets and split payouts

Guidelines

• Minimum 95 percent test coverage.
• Clear documentation and comments on fee vs holder share splitting.
• Timeframe: 96 hours.

[Baskarayelu]

I’d love to be assigned this issue and contribute across the relevant areas, whether it involves smart contracts, UI development, backend logic, design implementation, or overall system integration. I’m comfortable working across the full stack and can adapt to the project’s technical requirements to ensure a smooth and consistent contribution.