Create Cross-Network Deployment Scripts

[Yunusabdul38]

Description

Develop a set of scripts (e.g., using Bash or Node.js) to automate the deployment of PrediFi contracts across Stellar Testnet and Mainnet, including initialization and configuration of initial parameters.

Tasks

• Create a scripts/deploy.sh for standard deployments.
• Automate contract initialization post-deployment.
• Store and manage contract IDs for different environment stages.

Dependencies

• Issue Standardize Workspace and Crate Structure #300

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 150 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[abbakargarba]

@abbakargarba has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Application – #335 Create Cross-Network Deployment Scripts

Hi team,

I’d like to take this on.

I’ve successfully submitted 3 projects recently and I’m working steadily, focusing on clean, structured implementations, taking one task at a time to ensure reliability and maintainability.

For this task, I’ll:

• Create a scripts/deploy.sh script to handle standard deployments across Stellar Testnet and Mainnet
• Support environment-based configuration (e.g., .env.testnet, .env.mainnet)
• Automate post-deployment contract initialization (setting initial parameters, admin config, etc.)
• Store and manage contract IDs per environment in a structured way (JSON or env-based mapping)
• Ensure the script is safe, repeatable, and clearly logged

I’ll also account for dependency alignment with Issue #300 and structure the scripts so they’re easy to extend for future networks or staging environments.

The goal is to make deployments consistent, reproducible, and less error-prone.

Happy to get started and submit a clean, documented PR 🚀

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

[KevinMB0220]

@KevinMB0220 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi, I’m Kevin — a full-stack and smart contract engineer building on Stellar. I specialize in designing and shipping scalable, secure systems end-to-end, from Soroban smart contracts to production-ready backend infrastructure and user-facing applications.

I’ve worked on complex architectures involving automated agents, cross-chain logic, and data indexing, focusing on reliability, performance, and clean standards. My approach is very product-driven: I don’t just build contracts, I build complete systems that solve real user problems and can scale in production.

I’m especially interested in infrastructure, security, and automation — creating tools and frameworks that make it easier for other developers to build safely and efficiently on Stellar.

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

[Olowodarey]

@Olowodarey has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hello, I’m Darey Olowo, a frontend and smart contract developer with experience building and shipping reliable features. I’d like to take on this issue and deliver a solid solution within 24 hours.

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