v0.18.0 — wasm 6050d559f591277e487ed3c1a318906a4cb592059b45ea905412075bcdd44f82

Reproducible build

llama_cpp.wasm sha256	6050d559f591277e487ed3c1a318906a4cb592059b45ea905412075bcdd44f82
llama_cpp_canister commit	026bdf47d44541aec4a76bbfe797480e97df4945
llama_cpp_onicai_fork commit	91c63a2284ff99c5761a27c3865b312fb8eca148
built with	Docker, linux/amd64, icpp-pro 6.0.0
built on	2026-09-21

Reproduce this wasm yourself

git clone https://github.com/onicai/llama_cpp_canister.git
cd llama_cpp_canister
git checkout 026bdf47d44541aec4a76bbfe797480e97df4945
make docker-build-base
make docker-build-wasm

The last command prints the sha256. It must equal
6050d559f591277e487ed3c1a318906a4cb592059b45ea905412075bcdd44f82.

No Mac and no local toolchain are needed: the llama.cpp fork commit,
icpp-pro, wasi-sdk, Rust and Binaryen are all pinned inside the image.

Check what a deployed canister is running

Anyone can read a deployed module hash, with no special rights, from the
public read-state path:

dfx canister --network ic info <canister-id>

It must print Module hash: 0x6050d559f591277e487ed3c1a318906a4cb592059b45ea905412075bcdd44f82.

If you control the canister you can instead build and compare in one step:

make docker-verify-wasm VERIFY_CANISTER=<canister-id>

(That target uses icp canister status, a controller-only management
call; it fails with IC0542 for anyone else.)