`bump_storage` operator entrypoint wiring (operator-role only)

[ibrahimmosouf-png]

bump_storage operator entrypoint wiring (operator-role only)

Labels: api, cli, security, priority/low
Difficulty: Low · Effort: S
Backlog slot: 57

Problem Statement

bump_all_persistent(env, milestone_count) exists in storage.rs but no public entrypoint surfaces it.

Why it Matters

• Long-running campaigns require periodic TTL bumps to avoid Soroban storage archival.
• This ticket intentionally constrains the surface area; refer to Issue [MEDIUM] calculate_refund_amount uses debug_assert! and .expect() instead of typed errors #33 for the storage-layer authoritative design discussion. The exact split is: [MEDIUM] calculate_refund_amount uses debug_assert! and .expect() instead of typed errors #33 covers what (which keys, when, how often); this ticket covers how to invoke it externally (auth + CLI).

Security note: an "any caller can bump TTL" entrypoint would be a gas/DoS vector on storage rent. The new entrypoint must require an explicit operator role (e.g. OperatorData(Address) keyed set, authorised at initialize time) — not a public function.

Expected Outcome

• pub fn bump_storage(env: Env, operator: Address) requires operator.require_auth() AND that operator ∈ DataKey::Operators.
• orbitchain-cli bump-storage --id <CID> --operator-secret-key <S> invokes it.

Acceptance Criteria

• Caller without operator role panics with Error::Unauthorized.
• CLI option works end-to-end against a freshly authorized operator.

Files Likely Affected

• campaign/src/lib.rs, campaign/src/storage.rs, crates/tools/src/main.rs

Dependencies

Issue #33 (storage layer), Issue #5 (admin multi-sig).

---

[AnnieIj]

Hi! I'd love to work on this issue.

I plan to implement the bump_storage operator entrypoint wiring with operator-role access only, ensuring it aligns with the existing contract architecture, includes the necessary tests, and follows the project's conventions. Could you please assign this issue to me?

[armandocodecr]

Hi, I'm Armando, a Full-Stack Developer with solid experience building Soroban smart contracts in Rust, including storage/TTL management, role-based authorization, and CLI tooling around contracts.

My plan would be: add an Operators entry to DataKey if it doesn't already exist, implement pub fn bump_storage(env: Env, operator: Address) in campaign/src/lib.rs that calls operator.require_auth(), checks membership in the operator set, panics with Error::Unauthorized otherwise, and then calls the existing bump_all_persistent from storage.rs. On the CLI side, add the bump-storage --id --operator-secret-key command in crates/tools/src/main.rs, signing and invoking the entrypoint with the provided operator key. I'll also add a couple of tests covering an unauthorized caller panicking and a happy path against a freshly authorized operator, keeping the change scoped to invocation/auth as intended, without touching the storage-layer design from Issue #33.

[grantfox-oss]

🦊 GrantFox — @armandocodecr has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

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

Good luck! Track your progress on GrantFox.