Motoko WASM size diagnosing - Part 2

[skilesare]

Probably not as “easy” of a solution, but if we do a couple of things, this is what the icrc-118 and 120 suite was made for.

Ideal scenario:

1. Maybe work with @ZenVoich to set up a way for mops to publish a wasm to your chosen namespace on 118 wasm registry canister(or maybe a seperate cli?)
2. We need a thin shim utility class that can create a canister with cycles, set a 120 wasm orchestration canister to be the controller and then instruct a 120 wasm orchestrator to deploy the class with args and poll for it to be finished.
3. Fire an event that your canister is installed—remove the 120 controller if you want or leave it for easy upgrades if you deploy new versions with migration.

ICRC-118 – Wasm Registry Definition for Version Control and History

ICRC-118 – Wasm Registry Definition for Version Control and History [image] I’m pleased to share the initial draft of ICRC-118, which establishes a robust framework for managing WebAssembly (Wasm) modules on the Internet Computer. Purpose & Rationale: The core motivation behind ICRC-118 is to provide a transparent, auditable, and interoperable framework for Wasm module management on the Internet Computer. By ensuring that every change to a wasm is securely recorded, the specification builds …

ICRC-120 – Canister Wasm Orchestration Service

ICRC-120 – Canister Wasm Orchestration Service [image] I’m excited to share the initial draft of ICRC-120, a specification that defines a standardized interface for orchestrating WebAssembly (Wasm) module management on the Internet Computer. This framework covers the entire canister lifecycle—from installation and upgrade to rollback and configuration—ensuring smooth, consistent, and auditable transitions. This is especially critical for the AstroFlora project, which leverages standardized can…

@yrgg has Prometheus using this stack.