[SC-37] Harden the release profile for smaller deployable WASM

[yusuftomilola]

Overview

contracts/Cargo.toml sets only:

[profile.release]
opt-level = "z"
overflow-checks = true

Missing are lto, strip, codegen-units, and panic — all of which materially reduce WASM size. Soroban charges by resource usage and enforces size limits, and assetsup at 8,894 lines is the crate most at risk.

Tasks

• Add lto = true, codegen-units = 1, strip = "symbols", debug = 0, and panic = "abort".
• Keep overflow-checks = true — it is a safety property worth its cost in value-handling contracts.
• Add a release-with-logs profile inheriting release with debug-assertions = true for debugging on testnet.
• Measure and record WASM size per contract before and after in the PR.
• Verify all tests still pass and behaviour is unchanged under panic = "abort".

Acceptance Criteria

• Release profile includes the size optimizations.
• Measured WASM size reduction is documented per contract.
• cargo test --all passes unchanged.

Dependencies

Pairs with [SC-34] and [SC-46].

Notes for Contributors

Requires Rust + Soroban. Workspace: contracts/ (soroban-sdk 22, members: assetsup, contrib, multisig-wallet, multisig_transfer, asset-maintenance). Run cargo test --all, cargo fmt --all -- --check, and cargo clippy --all-targets --all-features -- -D warnings before opening a PR — CI enforces all three. Comment below to be assigned.

[fathiaoyinloye]

Hi, I'd like to work on this issue. I have relevant experience with the technologies and concepts involved, and I'm confident I can make the necessary implementation to ensure the it meets the acceptance criteria. I'd be happy to contribute to this task.

[midenotch]

@midenotch has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I've reviewed the task and have a clear implementation plan. Looking forward to contributing with a quality PR.

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

[amberly-d]

@amberly-d has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

can i solve this?

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

[drips-wave]

Congratulations, @amberly-d! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @amberly-d: 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 🌊