Invoice Creator Migration

[Kingsman-99]

Description

When a creator account is compromised or an invoice is transferred as part of a business handover, there is no on-chain path to reassign the creator role, forcing the original account to remain the sole authorized administrator indefinitely. The contract needs a two-step creator migration — nomination by the current creator followed by explicit acceptance by the successor — to prevent accidental or coerced transfers.

Technical Context

contracts/split/src/lib.rs — add nominate_new_creator(invoice_id: u64, successor: Address) and accept_creator_role(invoice_id: u64) #[contractimpl] entry points; contracts/split/src/storage.rs — add DataKey::PendingCreator(u64) to hold the nominated address until acceptance; contracts/split/src/auth.rs — env.require_auth(&current_creator) in nominate_new_creator, env.require_auth(&pending_creator) in accept_creator_role; contracts/split/src/events.rs — emit creator_nominated(invoice_id, successor) and creator_migrated(invoice_id, old, new).

Acceptance Criteria

• nominate_new_creator() writes successor to DataKey::PendingCreator(invoice_id) and requires auth from the current Invoice.creator
• accept_creator_role() overwrites Invoice.creator with the pending address, deletes DataKey::PendingCreator, and requires auth from the nominated successor
• A third address calling accept_creator_role() is rejected by the require_auth check without mutating state
• The current creator can cancel or replace a pending nomination by calling nominate_new_creator() again with a different address
• Tests in contracts/split/src/tests/creator_migration_tests.rs cover: successful two-step migration, unauthorized acceptance, nomination override, and acceptance on a deleted invoice (must return Error::InvoiceNotFound)
• All CI checks (cargo build --target wasm32-unknown-unknown, cargo test, cargo clippy) pass and the branch has no merge conflicts

---

[khanavi272-spec]

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

I would like to work on this issue

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

[adeniran19-maker]

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

I'm a full-stack developer and I'd like to take this issue.
I understand the requirements and will follow the existing project structure, keep the implementation clean, and include proper tests where applicable.

ETA: 1–3 days (depending on scope)

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

[Enemuo-debug]

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

Can I please work on this?

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

[drips-wave]

Congratulations, @adeniran19-maker! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

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