#086: Soroban WASM Size Reduction & AssemblyScript Porting Review

[bakarezainab]

#86: Soroban WASM Size Reduction & AssemblyScript Porting Review

Overview

Audit and optimize WASM compiler structures, refactoring heavy library calls into micro-sized helpers to fit within Soroban limits.

Objectives

• Run detailed WASM size profiling on current binaries.
• Replace heavy standard libraries with lightweight alternatives.
• Reduce compiled WASM footprint below 45KB.

Acceptance Criteria

• WASM size profiling reports.
• Refactored code showing measurable binary size reduction.
• 100% test suite compatibility.

[Theophilus131]

assign this to me

[Queenode]

I’d like to work on #77 because it combines smart-contract development with performance optimization, an area I’m particularly interested in exploring further within the Soroban ecosystem.

Implementation Approach

I would begin by establishing a baseline for the current contract binaries and generating WASM size reports so that optimization decisions are based on measurable results.

My approach would be:

1. Profile the current WASM binaries and identify the largest contributors to the final artifact.
2. Inspect dependency usage and identify heavy library calls that can be replaced with smaller, purpose-built helpers.
3. Refactor only the code paths contributing meaningfully to the WASM footprint.
4. Evaluate compiler/build configuration options that can reduce the final binary size without affecting contract behavior.
5. Where AssemblyScript porting is relevant, compare the resulting implementation and generated WASM rather than assuming a port will automatically produce a smaller binary.
6. Measure the binary after each significant change to verify the actual reduction.

The target would be to reduce the compiled WASM footprint below 45KB while keeping the contract's existing functionality intact.

Validation

I would provide:

• Before-and-after WASM size measurements.
• A report identifying the main sources of binary bloat.
• The refactored implementation and rationale for each optimization.
• Tests confirming that existing contract behavior remains unchanged.
• Final verification that the optimized WASM stays within the required size target.

I would prioritize measurable optimizations over premature refactoring and ensure the complete existing test suite continues to pass throughout the process.

[Rampop01]

I’m interested in working on this because it combines Soroban smart-contract development with WASM optimization.

I have experience with Rust, WebAssembly-based development, and smart contracts. I’d start by profiling the current WASM binary to identify the largest contributors to its size, then replace or refactor heavy dependencies where possible.

My focus would be on:

• Profiling and documenting the current WASM size.
• Reducing unnecessary dependencies and heavy library calls.
• Testing lightweight alternatives and compiler optimizations.
• Measuring the binary after each change.
• Ensuring the full test suite continues to pass.

My goal would be to achieve a measurable reduction toward the 45KB target without changing existing contract behavior.

[grantfox-oss]

🦊 GrantFox — @Rampop01 has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #86)
2. Your PR will be reviewed by the LatterFixxx maintainers

Good luck! Track your progress on GrantFox.