Set up Automated WASM Size Checking in CI

[Yunusabdul38]

Description

Integrate a check in the GitHub Actions workflow to monitor the size of the compiled WASM file. This ensures the contract remains within Soroban's limits and alerts developers to regressions.

Tasks

• Add a step to .github/workflows/ to build and check WASM size.
• Set a threshold and cause build failure if exceeded.
• Log artifacts of the build sizes over time.

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

[Emmanuelluxury]

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

I’d like to work on this issue because it sits at the intersection of system design, financial logic, and secure contract architecture — areas I actively specialize in and enjoy building within. The problem requires careful handling of state transitions, precision math, and security constraints, which makes it both technically meaningful and impactful to the overall reliability of the protocol.

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

[abdegenius]

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

I will love to work on this issue

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

[drips-wave]

Congratulations, @abdegenius! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

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