Add contract deployment script for testnet and mainnet

[ogazboiz]

Join our community: https://t.me/+DOylgFv1jyJlNzM0

Description

No automated deployment script exists. Developers must manually run multiple stellar CLI commands in sequence, which is error-prone and not repeatable.

What Needs to Happen

• Create scripts/deploy.sh:
  1. Build WASM: cargo build --target wasm32-unknown-unknown --release
  2. Optimize: stellar contract optimize
  3. Deploy: stellar contract deploy
  4. Initialize: stellar contract invoke ... initialize --admin ... --treasury ... --fee_rate_bps ...
  5. Save contract ID to deployment-info.json
• Support --network testnet|mainnet flag
• Validate required env vars before running
• Document in README under "Deployment"

Files

• scripts/deploy.sh (create)

Acceptance Criteria

• Single command deploys and initializes to testnet
• Contract ID saved to deployment-info.json
• Missing env vars cause a clear error before any action

[0xElyte]

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

I would love to resolve this

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

[akintewe]

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

I've been creating intricate forms and e-commerce systems for more than four years as a full-stack developer. I have designed inventory management systems for agricultural enterprises and have experience with image processing and large-scale state management. I have also worked on this project in the past.
My ETA is one hour, and I would love to work on this problem.

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

[anonfedora]

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

I'm Anonfedora, I have vast experience in contributing and building on the Stellar ecosystem with the Rust using soroban's SDK.
I'm also good at comprehensively testing features.
ETA: < 12 hours

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

[drips-wave]

Congratulations, @anonfedora! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

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

[drips-wave]

This issue has been completed by @anonfedora as part of the Stellar Wave Program's 4th Wave 🥳

😎 @anonfedora: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.