Stellar deployment script (testnet / futurenet / mainnet)

[truthixify]

Labels: Stellar Wave, stellar, feature, tooling, drips, help-wanted
Tier: M (2–4 days)
Type: feature / tooling

Context

The EVM side has evm/scripts/deploy.ts that deploys all five Solidity contracts in order and writes addresses to a deployments file. The Stellar side has no equivalent. Every deploy today is a manual soroban-cli ritual that depends on tribal knowledge.

We need a reproducible, network-aware deployment script.

Scope

Build contracts/stellar/scripts/deploy.ts (TypeScript via tsx/bun) — or deploy.rs if you prefer the Stellar Rust SDK — that:

1. Accepts a --network flag: testnet | futurenet | mainnet.
2. Reads the source identity from ~/.config/soroban/identities/<name>.toml or a flag.
3. Builds (stellar contract build) each contract crate if not already built.
4. Optimizes the WASM (stellar contract optimize).
5. Uploads the WASM, instantiates the contract, and captures the resulting contract ID.
6. Wires inter-contract references (stealth-sender.init(announcer_contract_id)).
7. Writes contracts/stellar/deployments/<network>.json with:

   {
     "network": "testnet",
     "deployer": "G...",
     "deployedAt": "2026-05-22T18:00:00Z",
     "contracts": {
       "stealthAnnouncer": "C...",
       "stealthRegistry": "C...",
       "stealthSender": "C...",
       "wraithNames": "C..."
     }
   }

8. Re-emits the deployments file to the SDK so getDeployment('stellar') picks it up (or document the SDK PR that needs to follow).

Bonus

• A --dry-run mode that prints planned operations without spending fees.
• Idempotency: if a deployment file already exists for the target network, refuse to overwrite without --force.
• Verification step that calls a read-only function on each freshly deployed contract and confirms a sane response.

Acceptance criteria

• Script runs cleanly against futurenet end-to-end in CI (or in a documented manual run).
• deployments/futurenet.json checked in.
• README updated with usage examples (pnpm deploy:stellar -- --network futurenet).
• Failure modes documented (insufficient balance, missing identity, RPC rate limits).

Resources

• Stellar SDK for TS: https://stellar.github.io/js-stellar-sdk/
• soroban-cli reference: https://developers.stellar.org/docs/tools/cli/stellar-cli

[sudo-robi]

Hi @truthixify i haven't been assigned to help you with this issue, please assign me

[thebabalola]

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

Hi maintainer, I'm a Stellar developer with extensive experience building deployment scripts and tooling. I can build a reproducible, network-aware deployment script for the Wraith Stellar contracts, ensuring that the deployment process is standardized and easily executable. Ready to dive in once assigned!

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

[drips-wave]

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

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