Repository navigation
Makefile deploy targets deploy the unoptimised .wasm — stellar contract optimize writes *.optimized.wasm #567
Description
Problem
make build runs stellar contract optimize --wasm $(WASM_DIR)/<name>.wasm. With no --wasm-out, stellar-cli writes <name>.optimized.wasm next to the input. The deploy-escrow/-milestones/-maintenance-pool targets then deploy $(WASM_DIR)/mergefi_escrow.wasm and friends, i.e. the unoptimised build. The optimisation step costs build time and the larger artifact is what gets deployed, with higher upload fees and a risk of exceeding size limits.
Suggested fix
Deploy the .optimized.wasm files (or pass --wasm-out to overwrite in place), and print artifact sizes in make build.
Activity
urielit1313-creator commentedon Oct 13, 2026
Submitted PR #572 resolving this issue.
Details
deploy-escrow,deploy-milestones, anddeploy-maintenance-pooltargets to deploy$(WASM_DIR)/mergefi_<name>.optimized.wasm.make builddisplaying the exact byte footprint of each optimized contract artifact.Payout Address (Base USDC):
0xfE777c43e4B0A24fFA1527eD520d1E7f9ECED483fix(makefile): deploy optimized wasm and print artifact sizes (MergeF…