v0.22.0 — wasm acb02b81a91b281f6514704b9acb0c4a6cfe0d992ca12381dbc11140e1dbc7ee

Reproducible build

llama_cpp.wasm sha256	acb02b81a91b281f6514704b9acb0c4a6cfe0d992ca12381dbc11140e1dbc7ee
llama_cpp_canister commit	98bd602c3dfaa89bff830b403c8b1b8d665ee966
llama_cpp_onicai_fork commit	f62e2a45b2548cc6b9027037bac6d19b5a3526ed
built with	Docker, linux/amd64, icpp-pro 6.3.2
built on	2026-10-14

Reproduce this wasm yourself

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

The last command prints the sha256. It must equal
acb02b81a91b281f6514704b9acb0c4a6cfe0d992ca12381dbc11140e1dbc7ee.

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: 0xacb02b81a91b281f6514704b9acb0c4a6cfe0d992ca12381dbc11140e1dbc7ee.

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.)