Docs / On-chain builds
On-chain builds
Build in a canister on the Internet Computer, so anyone can verify what you deploy.
| Page | What it covers |
|---|---|
| On-chain builds overview | Compile Motoko inside a canister on the Internet Computer, so anyone can check which source produced a wasm. |
| Your first on-chain build | Run moxzi build --remote, choose the identity that pays, and read what it prints. |
| Verifying a build | Check what the compiler canister built, from which files, and with which compiler. |
| Publishing to a registry | Publish a wasm to an ICRC-118 registry with its build record, so installers can see whether it was built on-chain. |
| How on-chain builds run | Why an on-chain build takes minutes, what the compiler canister does at each stage, and what it keeps afterwards. |
| Payment | How an on-chain build is priced, paid for in ICP, and refunded. |
| Sources and packages | How source files reach the compiler canister, the storage limits, and building from registered mops packages without uploading them. |
| Linking and installing | What linking does to an on-chain build's output, and how to install the result. |
| Trust | What each way of building and running moxzi actors asks you to trust, and what an on-chain build proves. |
If you only read one page, read On-chain builds overview.