v0.16.8 — wasm 3db909db346b6851ae1761de45b1fbc13b882ac0dbc3c44069f6944667e55066

Reproducible build

llama_cpp.wasm sha256	3db909db346b6851ae1761de45b1fbc13b882ac0dbc3c44069f6944667e55066
llama_cpp_canister commit	365e9f38120453aaa30d3c41f6e6b357c2fcd4bf
llama_cpp_onicai_fork commit	6bd774370579b0c48b8ad3f56df468907d033fe9
built with	Docker, linux/amd64, icpp-pro 6.0.0
built on	2026-09-15

Reproduce this wasm yourself

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

The last command prints the sha256. It must equal
3db909db346b6851ae1761de45b1fbc13b882ac0dbc3c44069f6944667e55066.

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

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