Developer Prompts DFINITY Discussion Over ICP Wasm Module and Function Limits

A developer working on the Toko project has submitted a technical inquiry to DFINITY’s execution and replica teams on the official developer forum, seeking clarification and a potential review of current WebAssembly (Wasm) resource limits on the Internet Computer.

The inquiry specifically highlights the platform's documented 10 MiB Wasm code-section limit and 50,000 declared function limit. According to the developer, the Toko Project Instance build slightly exceeds the documented 10 MiB code-section ceiling and is approaching the 50,000 function threshold, despite extensive footprint optimizations. While the project uses only 183 exported service methods—well below the 1,000 exported method limit—the internal Rust compiler outputs expand the Wasm function count through serialization code, async wrappers, and embedded libraries such as IcyDB and Canic.

The developer also highlighted a potential mismatch between documentation and codebase limits, referencing code within the dfinity/ic repository that sets MAX_CODE_SECTION_SIZE_IN_BYTES to 12 MiB. The post asks DFINITY to clarify whether production subnets enforce 10 MiB or 12 MiB and whether increasing the limit to 12 MiB or raising the function threshold could be benchmarked against compiler validation and host performance costs.