Repository navigation
[v2][contracts] Per-contract WASM size budgets enforced in CI #1229
Description
Activity
@IjayAbby has applied to work on this issue as part of the Stellar Wave Program's 8th wave.
Hello, I would love to work on this issue.
Max ETA to complete the task is 4 hours.ℹ️ Repo Maintainers: To accept this application, review their application or assign @IjayAbby to this issue.
Congratulations, @IjayAbby! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.
🧑💻 @IjayAbby: 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 🌊
Context
The release profile already optimises for size (
opt-level = "z",lto,strip), but nothing prevents a change from doubling a contract's WASM. Deployment cost and instruction limits on Soroban make silent size growth a real operational risk, and the shared-crate refactor makes it more likely.Scope
contracts/size-budgets.json.Acceptance criteria
contracts/size-budgets.jsonholds a byte budget per contract.Files / areas
.github/workflows/contracts.yml,contracts/size-budgets.jsonPart of the SYNCRO v2 rewrite. Epic: A — Contract foundation.