Invoice Batch Creation in a Single Transaction

[Kingsman-99]

Description

Creators who issue many invoices simultaneously (e.g. for a multi-track project) currently must submit individual transactions. A batch_create_invoices method should create up to N invoices atomically, returning all new invoice IDs.

Technical Context

Add batch_create_invoices(invoices: Vec<InvoiceParams>) -> Vec<u64> to contracts/split/src/lib.rs. Define InvoiceParams struct in types.rs mirroring create_invoice parameters. Iterate and call the internal _create_invoice helper for each entry. Enforce a MaxBatchSize cap stored in storage::instance. Emit BatchInvoiceCreated(ids: Vec<u64>) from events.rs.

Acceptance Criteria

• All invoices in the batch are created or none are (atomic failure)
• Returned Vec<u64> contains one new invoice_id per input entry, in order
• Batch size exceeding MaxBatchSize returns BatchTooLarge
• Each created invoice emits an individual InvoiceCreated event plus one BatchInvoiceCreated
• Creator invoice count cap is checked and updated atomically across the whole batch
• All CI checks (cargo build --target wasm32-unknown-unknown, cargo test, cargo clippy) pass and the branch has no merge conflicts

---

[Samaro1]

Gm gm boss. I would like to take this one on. I can implement batch_create_invoices with the InvoiceParams struct in types.rs, iterating through the internal _create_invoice helper atomically, enforce the MaxBatchSize cap returning BatchTooLarge when exceeded, emit both individual InvoiceCreated events and the batch InvoiceCreated event, and confirm the creator invoice count cap stays consistent across the batch while passing all CI checks. Please assign it to me.

[senmalong]

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

hi,

I’d love to take this issue on. I’m a smart contract and full-stack developer with experience across OnlyDust, Drips Waves 1–5, and the GrantFox beta campaign.

My stack includes Rust, Soroban, Cairo, Solidity, and TypeScript. I can deliver a clean, tested, and well-documented solution within 24 hours of assignment.

Happy to start immediately.

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