Upgrade the Registry Canister to Commit 00e4d8e
#144845 · Open · 3 d left · proposed Nov 16, 2026
Summary
Upgrade the Registry Canister to Commit 00e4d8e
__Proposer__: daniel.wong at dfinity.org
__Source code__: [00e4d8e3ee6081c1862e6119d63cffa76bd4af3d][new-commit]
[new-commit]: https://github.com/dfinity/ic/tree/00e4d8e3ee6081c1862e6119d63cffa76bd4af3d
Features & Fixes
Removed
- The deprecated
height,timeandstate_hashfields ofCatchUpPackageContents. Where
applicable, their equivalents are now found in cup_type: a CupType::Recovery record carries them in its RecoveryArgs, and the height of a CupType::Genesis CUP is always 0.
Security
update_node_operator_config_directlyno longer lets a node provider hand one of its node
operators to an arbitrary principal. The new node provider must already be the node provider of some node operator record, i.e. a principal the NNS introduced through an AddNodeOperator or UpdateNodeOperatorConfig proposal. Assigning a node operator to a brand-new node provider now requires an UpdateNodeOperatorConfig proposal. Previously, a node provider could move a node operator to any principal it chose, and back again, without any NNS involvement, which affects which node provider a day's node performance is attributed to for node rewards.
New Commits
$ git log --format="%C(auto) %h %s" 3e645182ac06c7b761040615db4e3d44a8349351..00e4d8e3ee6081c1862e6119d63cffa76bd4af3d -- ./rs/registry/canister
eecca7d2f5e fix(registry): only allow direct node operator reassignment to known node providers (#11975)
4c115dfc3d8 chore(registry): [CON-1671] remove `height`, `time`, `state_hash` from `CatchUpPackageContents` records in the registry (#11628)
4920b2657bb refactor: name the SEV-SNP launch measurement length (#11135)
9d8d74e6f4a chore(nervous-system): Update changelog for release 2026-10-23 (#11937)
Current Version
__Current git hash__: 3e645182ac06c7b761040615db4e3d44a8349351
__Current wasm hash__: 70cdfb7a9d190686d1a3ad0e1e85349111483f953557b97aa7ecfa57d578d0e4
Verification
See the general instructions on [how to verify] proposals like this. A "quick start" guide is provided here.
[how to verify]: https://github.com/dfinity/ic/tree/00e4d8e3ee6081c1862e6119d63cffa76bd4af3d/rs/nervous_system/docs/proposal_verification.md
WASM Verification
See ["Building the code"][prereqs] for prerequisites.
# 1. Get a copy of the code.
git clone git@github.com:dfinity/ic.git
cd ic
# Or, if you already have a copy of the ic repo,
git fetch
git checkout 00e4d8e3ee6081c1862e6119d63cffa76bd4af3d
# 2. Build canisters.
./ci/container/build-ic.sh -c
# 3. Fingerprint the result.
sha256sum ./artifacts/canisters/registry-canister.wasm.gz
This should match wasm_module_hash field of this proposal.
Official view: dashboard.internetcomputer.org/proposal/144845