Repository navigation
v0.23.0rc5 — wasm 8c602fa56de7e4b53b795bb4625b827ba84c8c2fa94b75d76e6873930e6b474d
Pre-releaseOverview
v0.23.0rc5 is the fifth release candidate of v0.23.0: v0.23.0rc4 rebuilt on icpp-pro 7.0.0rc7, the candidate for icpp-pro 7.0.0. Its Candid decoder traps on invalid or abusive messages instead of reading out of bounds or hanging. Nothing else changes since rc4, except that a client that sends a vec of another element type than the .did declares now gets a trap.
Highlights
- Hardened Candid decoder: spec-invalid or abusive messages trap instead of reading out of bounds or hanging (#72)
Behaviour changes for apps
- A vec must have the element type the
.diddeclares: e.g. avec textwhere avec nat8is expected now traps (#72) - New limits per message: a nesting depth of 128, and 1,000,000 values that take no bytes on the wire (#72)
Upgrade notes
- Upgrade every canister built from v0.23.0rc4 or earlier; an upgrade from rc4 keeps the uploaded models (#72)
- Some replies can be a few bytes smaller (an extra opt argument no longer adds its types): same values, different bytes (#72)
icpp-pro
- icpp-pro 7.0.0rc7, from 7.0.0rc4: the decoder hardening, faster decoding of wide records and vecs of variants (#72)
Changelog since v0.23.0rc4
Reproducible build
llama_cpp.wasm sha256 |
8c602fa56de7e4b53b795bb4625b827ba84c8c2fa94b75d76e6873930e6b474d |
| llama_cpp_canister commit | c7d22e55a650539040d6783625a372daf23cc5de |
| llama_cpp_onicai_fork commit | 702142008552e33844f99dddefc409550166d175 |
| built with | Docker, linux/amd64, icpp-pro 7.0.0rc7 |
| built on | 2026-10-29 |
Reproduce this wasm yourself
git clone https://github.com/onicai/llama_cpp_canister.git
cd llama_cpp_canister
git checkout c7d22e55a650539040d6783625a372daf23cc5de
make docker-build-base
make docker-build-wasmThe last command prints the sha256. It must equal
8c602fa56de7e4b53b795bb4625b827ba84c8c2fa94b75d76e6873930e6b474d.
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: 0x8c602fa56de7e4b53b795bb4625b827ba84c8c2fa94b75d76e6873930e6b474d.
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.)