Soroban storage entry recovery tooling

[truthixify]

Tier: M (2-4 days) Type: tooling

Context

Soroban storage entries get archived after TTL expiry. Recovery exists but is manual and error-prone. Build tooling that surfaces archived state and restores it with cost estimation.

Scope

• stellar/scripts/recover-storage.ts CLI
• Subcommands: list-archived <contract-id>, estimate-restore <key>, restore <key>
• Reads Stellar Expert API or RPC for archived entries
• Pre-computes XLM cost before restoring
• Idempotent restore (no-op if already live)
• Documentation

Acceptance criteria

• CLI implemented + tested against futurenet
• Cost estimator accurate
• Documentation in stellar/README.md
• Per-contract recovery procedure section

Files to start with

• New: stellar/scripts/recover-storage.ts
• Soroban state archival docs

[sublime247]

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

gm
I would like to work on this issue.

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

[drips-wave]

Congratulations, @sublime247! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

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

[truthixify]

@sublime247 Assigned. Welcome to wave 6.

Quick expectations to make this smooth for both sides:

1. Branch from develop (not main). PRs target develop.
2. Open a draft PR within ~3 days of pickup so we can see direction early.
3. Update at least every 5 days. If you get stuck or context changes, just say so on the PR — silence is the only thing that costs you the assignment.
4. Read the issue body's acceptance criteria carefully. Hitting those is the merge bar.

If anything is ambiguous, ask before building. Looking forward to the PR.