Join our community: https://t.me/+DOylgFv1jyJlNzM0
Description
There is no automated deployment script. The CI pipeline now builds and optimizes WASM, but deploying and initializing the contract still requires manual CLI commands.
What Needs to Happen
- Create
scripts/deploy.sh:
- Build WASM:
cargo build --target wasm32-unknown-unknown --release
- Optimize:
stellar contract optimize
- Deploy:
stellar contract deploy --wasm-hash ...
- Initialize:
stellar contract invoke ... initialize --admin ... --treasury ... --fee_rate_bps ...
- Save contract ID and tx hashes to
deployment-info.json
- Support
--network testnet|mainnet flag
- Validate required env vars before any action (
DEPLOYER_SECRET, TREASURY_ADDRESS, FEE_RATE_BPS)
- Document in README under "Deployment"
Files
scripts/deploy.sh (create)
Acceptance Criteria
Description
There is no automated deployment script. The CI pipeline now builds and optimizes WASM, but deploying and initializing the contract still requires manual CLI commands.
What Needs to Happen
scripts/deploy.sh:cargo build --target wasm32-unknown-unknown --releasestellar contract optimizestellar contract deploy --wasm-hash ...stellar contract invoke ... initialize --admin ... --treasury ... --fee_rate_bps ...deployment-info.json--network testnet|mainnetflagDEPLOYER_SECRET,TREASURY_ADDRESS,FEE_RATE_BPS)Files
scripts/deploy.sh(create)Acceptance Criteria
deployment-info.jsonupdated with contract ID