Proposals:

• Proposal ID: 138385

  Register a node provider 'Swiss Datalink AG', in line with the announcement and discussion at https://forum.dfinity.org/t/swiss-subnet-node-provider-onboarding-has-begun/55556/34. All documents below and their hashes are available on the IC Wiki (https://wiki.internetcomputer.org/wiki/Swiss_Datalink_AG). * Identity and Compliance Declaration: 041f23d59a9ec52104ce0aa034ca34da1b6e4e829cc0c349197e53993f50b1bf * Assessment of Independence: 9e1a0a00d3406f2a135890b54730b5e5187bc1c9a13b36fcaf6325a29cecef6f * Proof of Identity: ed0f51377ef98b8a12e7e00d9e60ee8eaba8dc8ecc7ccf901583ac5816223afb

• Proposal ID: 138384

  # Proposal to upgrade the Bitcoin canister Repository: `https://github.com/dfinity/bitcoin-canister.git` Git hash: `292b446a0ec64158eb2c68247530870ff201f274` New compressed Wasm hash: `42af59ae4fd5041f30f8ac12f324e3a93533de0cb89cd2278100c2389cbfff65` Upgrade args hash: `0fee102bd16b053022b69f2c65fd5e2f41d150ce9c214ac8731cfaf496ebda4e` Target canister: `ghsi2-tqaaa-aaaan-aaaca-cai` Previous Bitcoin canister proposal: https://dashboard.internetcomputer.org/proposal/132220 --- ## Motivation This proposal aims to upgrade the Bitcoin canister to incorporate several bug fixes, add metrics for better monitoring, and upgrade dependencies to their latest versions. ## Release Notes ``` git log --format='%C(auto) %h %s' release/2024-08-30.. -- canister b86ac5f fix: fix stuck canister after upgrade during block fetch (#405) a611575 feat(runtime): add mocking time (#401) 6167314 fix: adaptive max depth limit calculation for unstable blocks tree (#385) ee3d395 fix: [EXC-1987] Fix encoding of get_block_headers metrics on Bitcoin canister (#383) 82863a8 chore: adjust testnet unstable max depth difference (#382) b2177ec chore: cleanups (#381) 063beb8 fix: fix unstable tree block stability check for testnet (#379) ced4b1b fix: fix memory leak (#378) e19928c feat: add default fees for mainnet/testnet networks (#376) cbf67c8 chore: update dfx to 0.23 and rust to 1.81 (#372) f96124b chore: update get_successors metrics (#364) 0e9a055 fix: get_successors request sends unique hashes (#363) f63b04f feat: add get_successors_request_interval histogram metric (#361) 414a7fa feat: add get_successors request / response metrics for bitcoin canister (#360) 6f88899 fix: reduce Bitcoin canister logs by skipping full GetSuccessorsResponse (#359) 93213b2 chore: add instructions for generating testnet_blocks.txt (#351) 47c5d1f feat: upgrade bitcoin crate to 0.32.4 for testnet4 support (#349) 64f3183 fix: remove `rand` dependency from Bitcoin canister (#348) f7afb9d chore: Upgrade stable structures to 0.6.7 (#346) 32c70fa chore: rename usage of BlockHeader to Header for bitcoin crate v.0.32.4 update (#345) ``` ## Upgrade args ``` git fetch git checkout 292b446a0ec64158eb2c68247530870ff201f274 didc encode '()' | xxd -r -p | sha256sum ``` ## Wasm Verification Verify that the hash of the gzipped WASM matches the proposed hash. NOTE: This process is not yet guaranteed to match on Apple Silicon. ``` git fetch git checkout 292b446a0ec64158eb2c68247530870ff201f274 docker build -t canisters . docker run --rm canisters cat /ic-btc-canister.wasm.gz > ic-btc-canister.wasm.gz sha256sum ic-btc-canister.wasm.gz ```

• Proposal ID: 138383

  Update subnet tdb26-jop6k-aogll-7ltgs-eruif-6kk7m-qpktf-gdiqx-mxtrf-vb5e6-eqe to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138382

  # [αlpha-vote](https://dashboard.internetcomputer.org/neuron/2947465672511369) **αlpha-vote** is one of the 3 options provided by the **[ALPHA-Vote neuron automation system](https://forum.dfinity.org/t/alpha-vote-secure-your-stake-never-miss-a-vote/56826)**. ALPHA-Vote ensures the NNS gets the best out of its voters, while allowing voters to get the most out of the NNS. Voters who have **no intention** of reviewing a proposal topic manually should consider following αlpha-vote (or another neuron who uses this framework by following one of these 3 neurons) to guarantee that voting opportunities are never missed, and that voting rewards are always captured. αlpha-vote basically follows D-QUORUM (so it votes as soon as D-QUORUM votes), but will reject in the last 3 hours if D-QUORUM doesn’t vote. The difference between αlpha-vote and Ωmega-vote is that the former votes as soon as it can, and the latter votes as late as it can (while still reliably ensuring a vote is cast). This difference in behavior is where the alpha and omega naming convention comes from (first vs last). ### What problem does ALPHA-Vote aim to solve? There are notable examples where diligent voters have lost followees simply for missing an occasional vote. This dynamic is not helpful for encouraging high-quality due diligence and decentralization. This tendency of followers has been used as reasoning to diminish the size of the voting quorum of well-known neurons, including adding hotkeys which grant individuals unilateral control over otherwise community-controlled neurons. ALPHA-Vote aims to provide an alternative approach that does not compromise on security and decentralization. This solution allows diligent voters to take their time during reviews, safe in the knowledge that they will not accidentally miss the deadline in a way that leads to lost voting rewards. Followers commonly value knowing that their followee neuron will always vote, **no matter what**. ### How does ALPHA-Vote ensure a vote is never ever missed? ALPHA-Vote has multiple degrees of redundancy and fault tolerance built in. The system is spread across numerous different subnets, including the fiduciary subnet, so if one subnet stalls the others will pick up the slack. ### How does ALPHA-Vote deliver highly secure votes? ALPHA-Vote is deployed on the fiduciary subnet which is composed of 34 nodes. There are also fallback canisters that reside on smaller subnets, but these canisters are required to reach consensus before they can affect the final vote. This means multiple 13-node subnets would need to be attacked in order to affect the behavior of ALPHA-Vote, provided the 34-node fiduciary subnet has also been successfully attacked or stalled at the same time. Once ALPHA-Vote is finished, the main canister (on the fiduciary subnet) will be controlled by a large quorum of developers, notable governance participants and DFINITY engineers who are required to come to consensus in order to deploy updates. There is no anticipated need to deploy updates, except for unanticipated API changes that may occur in the future. The fallback canisters on the smaller subnets will be blackholed. Each of these control their own set of neurons, which each contribute to the final vote of the known neurons. If these blackholed canisters ever break (as a result of unanticipated API changes), the known neurons can be reconfigured to follow a fresh set of fixed blackholed canister controlled neurons. In the meantime, no votes would be missed as the blackholed canisters simply serve as an edge-case backstop (the main canister on the fiduciary subnet is capable of catching proposals and triggering votes by itself). Advanced users who would prefer immutable behavior (with the risk that it may break at some point in the future) can follow the blackholed canister neurons directly. ### How can I monitor the behavior of ALPHA-Vote canisters and neurons? Once the known neurons are adopted you can track the votes like any other known neuron, on the dashboard and via the governance canister. [All canisters](https://github.com/aodl/ALPHA-Vote/blob/master/canister_ids.json) also have publicly visible logs. -------- For more information about blackholing, decentralization and discussion about future developments (including autonomous perpetual cycles for added resilience), please visit the forum -> [ALPHA-Vote: Secure Your Stake, Never Miss a Vote ✅](https://forum.dfinity.org/t/alpha-vote-secure-your-stake-never-miss-a-vote/56826)

• Proposal ID: 138381

  # [Ωmega-vote](https://dashboard.internetcomputer.org/neuron/18363645821499695760) **Ωmega-vote** is one of the 3 options provided by the **[ALPHA-Vote neuron automation system](https://forum.dfinity.org/t/alpha-vote-secure-your-stake-never-miss-a-vote/56826)**. ALPHA-Vote ensures the NNS gets the best out of its voters, while allowing voters to get the most out of the NNS. Voters who intend to **sometimes** step in and vote on a specific topic should consider following Ωmega-vote. This ensures a diligent vote is cast by default (if D-QUORUM has voted), but also gives the follower the ability to vote manually for the vast majority of the voting period (should they decide to). If they end up not voting manually, D-QUORUM’s vote will be copied by Ωmega-vote within the last 3 hours of the proposal deadline (which will then trigger your neuron to vote the same way). If D-QUORUM didn’t vote either, then a default rejection will be triggered (in the same way as Ωmega-reject). ### What problem does ALPHA-Vote aim to solve? There are notable examples where diligent voters have lost followees simply for missing an occasional vote. This dynamic is not helpful for encouraging high-quality due diligence and decentralization. This tendency of followers has been used as reasoning to diminish the size of the voting quorum of well-known neurons, including adding hotkeys which grant individuals unilateral control over otherwise community-controlled neurons. ALPHA-Vote aims to provide an alternative approach that does not compromise on security and decentralization. This solution allows diligent voters to take their time during reviews, safe in the knowledge that they will not accidentally miss the deadline in a way that leads to lost voting rewards. Followers commonly value knowing that their followee neuron will always vote, **no matter what**. ### How does ALPHA-Vote ensure a vote is never ever missed? ALPHA-Vote has multiple degrees of redundancy and fault tolerance built in. The system is spread across numerous different subnets, including the fiduciary subnet, so if one subnet stalls the others will pick up the slack. ### How does ALPHA-Vote deliver highly secure votes? ALPHA-Vote is deployed on the fiduciary subnet which is composed of 34 nodes. There are also fallback canisters that reside on smaller subnets, but these canisters are required to reach consensus before they can affect the final vote. This means multiple 13-node subnets would need to be attacked in order to affect the behavior of ALPHA-Vote, provided the 34-node fiduciary subnet has also been successfully attacked or stalled at the same time. Once ALPHA-Vote is finished, the main canister (on the fiduciary subnet) will be controlled by a large quorum of developers, notable governance participants and DFINITY engineers who are required to come to consensus in order to deploy updates. There is no anticipated need to deploy updates, except for unanticipated API changes that may occur in the future. The fallback canisters on the smaller subnets will be blackholed. Each of these control their own set of neurons, which each contribute to the final vote of the known neurons. If these blackholed canisters ever break (as a result of unanticipated API changes), the known neurons can be reconfigured to follow a fresh set of fixed blackholed canister controlled neurons. In the meantime, no votes would be missed as the blackholed canisters simply serve as an edge-case backstop (the main canister on the fiduciary subnet is capable of catching proposals and triggering votes by itself). Advanced users who would prefer immutable behavior (with the risk that it may break at some point in the future) can follow the blackholed canister neurons directly. ### How can I monitor the behavior of ALPHA-Vote canisters and neurons? Once the known neurons are adopted you can track the votes like any other known neuron, on the dashboard and via the governance canister. [All canisters](https://github.com/aodl/ALPHA-Vote/blob/master/canister_ids.json) also have publicly visible logs. -------- For more information about blackholing, decentralization and discussion about future developments (including autonomous perpetual cycles for added resilience), please visit the forum -> [ALPHA-Vote: Secure Your Stake, Never Miss a Vote ✅](https://forum.dfinity.org/t/alpha-vote-secure-your-stake-never-miss-a-vote/56826)

• Proposal ID: 138380

  # [Ωmega-vote](https://dashboard.internetcomputer.org/neuron/18363645821499695760) **Ωmega-vote** is one of the 3 options provided by the **[ALPHA-Vote neuron automation system](https://forum.dfinity.org/t/alpha-vote-secure-your-stake-never-miss-a-vote/56826)**. ALPHA-Vote ensures the NNS gets the best out of its voters, while allowing voters to get the most out of the NNS. Voters who intend to **sometimes** step in and vote on a specific topic should consider following Ωmega-vote. This ensures a diligent vote is cast by default (if D-QUORUM has voted), but also gives the follower the ability to vote manually for the vast majority of the voting period (should they decide to). If they end up not voting manually, D-QUORUM’s vote will be copied by Ωmega-vote within the last 3 hours of the proposal deadline (which will then trigger your neuron to vote the same way). If D-QUORUM didn’t vote either, then a default rejection will be triggered (in the same way as Ωmega-reject). ### What problem does ALPHA-Vote aim to solve? There are notable examples where diligent voters have lost followees simply for missing an occasional vote. This dynamic is not helpful for encouraging high-quality due diligence and decentralization. This tendency of followers has been used as reasoning to diminish the size of the voting quorum of well-known neurons, including adding hotkeys which grant individuals unilateral control over otherwise community-controlled neurons. ALPHA-Vote aims to provide an alternative approach that does not compromise on security and decentralization. This solution allows diligent voters to take their time during reviews, safe in the knowledge that they will not accidentally miss the deadline in a way that leads to lost voting rewards. Followers commonly value knowing that their followee neuron will always vote, **no matter what**. ### How does ALPHA-Vote ensure a vote is never ever missed? ALPHA-Vote has multiple degrees of redundancy and fault tolerance built in. The system is spread across numerous different subnets, including the fiduciary subnet, so if one subnet stalls the others will pick up the slack. ### How does ALPHA-Vote deliver highly secure votes? ALPHA-Vote is deployed on the fiduciary subnet which is composed of 34 nodes. There are also fallback canisters that reside on smaller subnets, but these canisters are required to reach consensus before they can affect the final vote. This means multiple 13-node subnets would need to be attacked in order to affect the behavior of ALPHA-Vote, provided the 34-node fiduciary subnet has also been successfully attacked or stalled at the same time. Once ALPHA-Vote is finished, the main canister (on the fiduciary subnet) will be controlled by a large quorum of developers, notable governance participants and DFINITY engineers who are required to come to consensus in order to deploy updates. There is no anticipated need to deploy updates, except for unanticipated API changes that may occur in the future. The fallback canisters on the smaller subnets will be blackholed. Each of these control their own set of neurons, which each contribute to the final vote of the known neurons. If these blackholed canisters ever break (as a result of unanticipated API changes), the known neurons can be reconfigured to follow a fresh set of fixed blackholed canister controlled neurons. In the meantime, no votes would be missed as the blackholed canisters simply serve as an edge-case backstop (the main canister on the fiduciary subnet is capable of catching proposals and triggering votes by itself). Advanced users who would prefer immutable behavior (with the risk that it may break at some point in the future) can follow the blackholed canister neurons directly. ### How can I monitor the behavior of ALPHA-Vote canisters and neurons? Once the known neurons are adopted you can track the votes like any other known neuron, on the dashboard and via the governance canister. [All canisters](https://github.com/aodl/ALPHA-Vote/blob/master/canister_ids.json) also have publicly visible logs. -------- For more information about blackholing, decentralization and discussion about future developments (including autonomous perpetual cycles for added resilience), please visit the forum -> [ALPHA-Vote: Secure Your Stake, Never Miss a Vote ✅](https://forum.dfinity.org/t/alpha-vote-secure-your-stake-never-miss-a-vote/56826)

• Proposal ID: 138379

  # [Ωmega-reject](https://dashboard.internetcomputer.org/neuron/18422777432977120264) **Ωmega-reject** is one of the 3 options provided by the **[ALPHA-Vote neuron automation system](https://forum.dfinity.org/t/alpha-vote-secure-your-stake-never-miss-a-vote/56826)**. ALPHA-Vote ensures the NNS gets the best out of its voters, while allowing voters to get the most out of the NNS. Voters who have **every intention** of reviewing proposals for a specific topic manually should consider following Ωmega-reject. In principle an automatic rejection should never occur, but in the unlikely event that a manual vote is accidentally missed, a rejection will be automatically triggered at the end of the voting period (as your neuron will follow the *last-minute* vote of Ωmega-reject). ### What problem does ALPHA-Vote aim to solve? There are notable examples where diligent voters have lost followees simply for missing an occasional vote. This dynamic is not helpful for encouraging high-quality due diligence and decentralization. This tendency of followers has been used as reasoning to diminish the size of the voting quorum of well-known neurons, including adding hotkeys which grant individuals unilateral control over otherwise community-controlled neurons. ALPHA-Vote aims to provide an alternative approach that does not compromise on security and decentralization. This solution allows diligent voters to take their time during reviews, safe in the knowledge that they will not accidentally miss the deadline in a way that leads to lost voting rewards. Followers commonly value knowing that their followee neuron will always vote, **no matter what**. ### How does ALPHA-Vote ensure a vote is never ever missed? ALPHA-Vote has multiple degrees of redundancy and fault tolerance built in. The system is spread across numerous different subnets, including the fiduciary subnet, so if one subnet stalls the others will pick up the slack. ### How does ALPHA-Vote deliver highly secure votes? ALPHA-Vote is deployed on the fiduciary subnet which is composed of 34 nodes. There are also fallback canisters that reside on smaller subnets, but these canisters are required to reach consensus before they can affect the final vote. This means multiple 13-node subnets would need to be attacked in order to affect the behavior of ALPHA-Vote, provided the 34-node fiduciary subnet has also been successfully attacked or stalled at the same time. Once ALPHA-Vote is finished, the main canister (on the fiduciary subnet) will be controlled by a large quorum of developers, notable governance participants and DFINITY engineers who are required to come to consensus in order to deploy updates. There is no anticipated need to deploy updates, except for unanticipated API changes that may occur in the future. The fallback canisters on the smaller subnets will be blackholed. Each of these control their own set of neurons, which each contribute to the final vote of the known neurons. If these blackholed canisters ever break (as a result of unanticipated API changes), the known neurons can be reconfigured to follow a fresh set of fixed blackholed canister controlled neurons. In the meantime, no votes would be missed as the blackholed canisters simply serve as an edge-case backstop (the main canister on the fiduciary subnet is capable of catching proposals and triggering votes by itself). Advanced users who would prefer immutable behavior (with the risk that it may break at some point in the future) can follow the blackholed canister neurons directly. ### How can I monitor the behavior of ALPHA-Vote canisters and neurons? Once the known neurons are adopted you can track the votes like any other known neuron, on the dashboard and via the governance canister. [All canisters](https://github.com/aodl/ALPHA-Vote/blob/master/canister_ids.json) also have publicly visible logs. -------- For more information about blackholing, decentralization and discussion about future developments (including autonomous perpetual cycles for added resilience), please visit the forum -> [ALPHA-Vote: Secure Your Stake, Never Miss a Vote ✅](https://forum.dfinity.org/t/alpha-vote-secure-your-stake-never-miss-a-vote/56826)

• Proposal ID: 138378

  # Upgrade the Node-rewards Canister to Commit ca959ab __Proposer__: pietro.di.marco at dfinity.org __Source code__: [ca959ab71539b277af5f9880e6a4c5779e135cad][new-commit] [new-commit]: https://github.com/dfinity/ic/tree/ca959ab71539b277af5f9880e6a4c5779e135cad ## Features & Fixes * Add Node Provider filtering on get_rewardable_nodes_per_provider to reduce number of instruction on query calls. * Discard historical rewards storage and API endpoints as historical rewards will be stored in Governance canister. * Disable replicated execution of query calls. ## New Commits ``` $ git log --format="%C(auto) %h %s" e3857ed56a35a75170e6d93ed98b84c169860f72..ca959ab71539b277af5f9880e6a4c5779e135cad -- ./rs/node_rewards/canister ./rs/node_rewards ./rs/registry/node_provider_rewards 3f74b950e1 chore(NRC): Add NP filter for query calls (#6605) 9152ba15ab fix(NPR): Discard historical rewards storage and APIs (#6600) a1c2e2e556 chore(PocketIC): use Option<EmptyConfig> instead of bool and Option<bool> (#6549) 3d42cb0fee chore: disable replicated execution of query endpoints in NRC (#6521) ``` ## Current Version __Current git hash__: e3857ed56a35a75170e6d93ed98b84c169860f72 __Current wasm hash__: 3d33e8501e05b3387346152808f0adcbf401a789cb1c11b475c4ae7092fe6384 ## 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/ca959ab71539b277af5f9880e6a4c5779e135cad/rs/nervous_system/docs/proposal_verification.md ### WASM Verification See ["Building the code"][prereqs] for prerequisites. [prereqs]: https://github.com/dfinity/ic/tree/ca959ab71539b277af5f9880e6a4c5779e135cad/README.adoc#building-the-code ``` # 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 ca959ab71539b277af5f9880e6a4c5779e135cad # 2. Build canisters. ./ci/container/build-ic.sh -c # 3. Fingerprint the result. sha256sum ./artifacts/canisters/node-rewards-canister.wasm.gz ``` This should match `wasm_module_hash` field of this proposal.

• Proposal ID: 138377

  This is Internet Identity release [release-2025-09-05](https://github.com/dfinity/internet-identity/releases/tag/release-2025-09-05) for commit [fe188b51952dc0be24d2c7ed654d029670b082ca](https://github.com/dfinity/internet-identity/commit/fe188b51952dc0be24d2c7ed654d029670b082ca). This release enables the new landing page. Additionally, the popup that was blocked in Safari is fixed and an internal migration is added to improve the robustness of the backend (not visible to the users). The sha256 of production asset [internet_identity_production.wasm.gz](https://github.com/dfinity/internet-identity/releases/download/release-2025-09-05/internet_identity_production.wasm.gz) is [b34b15698385c6f3ec3fd217a44de7d247751379c996f8987cf08dd761032af2](https://github.com/dfinity/internet-identity/actions/runs/17491949779/job/49683568556#step:7:1). ## What's Changed * Bump tracing-subscriber from 0.3.19 to 0.3.20 by @dependabot[bot] in https://github.com/dfinity/internet-identity/pull/3333 * Fix popup blocked by Safari when linking openID accounts by @lmuntaner in https://github.com/dfinity/internet-identity/pull/3334 * feat: Extend memory layout to support `lookup_application_with_origin` keyed by full SHA-256 sums by @aterga in https://github.com/dfinity/internet-identity/pull/3329 * Add sign up with OIDC e2e tests. by @sea-snake in https://github.com/dfinity/internet-identity/pull/3335 * Remove unused options param to AddAccessMethodFlow by @lmuntaner in https://github.com/dfinity/internet-identity/pull/3336 * chore: Implement data migration for `lookup_application_with_origin_map` by @aterga in https://github.com/dfinity/internet-identity/pull/3337 * first by @aterga in https://github.com/dfinity/internet-identity/pull/3343 * Landing Page by @danblackadder in https://github.com/dfinity/internet-identity/pull/3341 ## New Contributors * @danblackadder made their first contribution in https://github.com/dfinity/internet-identity/pull/3341 **Full Changelog**: https://github.com/dfinity/internet-identity/compare/release-2025-08-29...release-2025-09-05 ## Build flavors For more information please see the [Build flavors](https://github.com/dfinity/internet-identity/tree/release-2025-09-05#build-features-and-flavors) section of the README. | Filename | sha256 (links to CI Run) | | --- | --- | |[internet_identity_production.wasm.gz](https://github.com/dfinity/internet-identity/releases/download/release-2025-09-05/internet_identity_production.wasm.gz)|[`b34b15698385c6f3ec3fd217a44de7d247751379c996f8987cf08dd761032af2`](https://github.com/dfinity/internet-identity/actions/runs/17491949779/job/49683568556#step:7:1)| |[internet_identity_dev.wasm.gz](https://github.com/dfinity/internet-identity/releases/download/release-2025-09-05/internet_identity_dev.wasm.gz)|[`48847e1ad541e9c5ef431582ca442382efb690510fc11ee8cd4c99d550b7d3ed`](https://github.com/dfinity/internet-identity/actions/runs/17491949779/job/49683568615#step:7:1)| |[internet_identity_test.wasm.gz](https://github.com/dfinity/internet-identity/releases/download/release-2025-09-05/internet_identity_test.wasm.gz)|[`ff86b904f613a34359f3aa09ded3058bd6e4e61abcb28f3b2533f9f2bdc667e9`](https://github.com/dfinity/internet-identity/actions/runs/17491949779/job/49683568547#step:7:1)| |[archive.wasm.gz](https://github.com/dfinity/internet-identity/releases/download/release-2025-09-05/archive.wasm.gz)|[`e4ff848a8a3dfb7ee1c2708fc2df982928b0023ec2a777a7ccae52594db3679f`](https://github.com/dfinity/internet-identity/actions/runs/17491949779/job/49683568573#step:6:1)| |[vc_demo_issuer.wasm.gz](https://github.com/dfinity/internet-identity/releases/download/release-2025-09-05/vc_demo_issuer.wasm.gz)|[`58e4ab2b2e885959248370c318e4ae7a9398c47e35c14e36ee1e056043b0889b`](https://github.com/dfinity/internet-identity/actions/runs/17491949779/job/49683538432#step:8:1)| ## Wasm Verification To build the wasm modules yourself and verify their hashes, run the following commands from the root of the [Internet Identity repository](https://github.com/dfinity/internet-identity): ``` git pull # to ensure you have the latest changes. git checkout fe188b51952dc0be24d2c7ed654d029670b082ca ./scripts/verify-hash --ii-hash b34b15698385c6f3ec3fd217a44de7d247751379c996f8987cf08dd761032af2 --archive-hash e4ff848a8a3dfb7ee1c2708fc2df982928b0023ec2a777a7ccae52594db3679f ``` Make sure to compare the hashes also with the proposal payload when verifying canister upgrade proposals. ## Argument Verification Run the following command to verify the upgrade argument hash: ``` didc encode '( opt record { fetch_root_key = null; openid_google = null; is_production = null; enable_dapps_explorer = null; assigned_user_number_range = null; new_flow_origins = null; archive_config = opt record { polling_interval_ns = 15_000_000_000 : nat64; entries_buffer_limit = 10_000 : nat64; module_hash = blob "\e4\ff\84\8a\8a\3d\fb\7e\e1\c2\70\8f\c2\df\98\29\28\b0\02\3e\c2\a7\77\a7\cc\ae\52\59\4d\b3\67\9f"; entries_fetch_limit = 1_000 : nat16; }; canister_creation_cycles_cost = null; analytics_config = null; feature_flag_enable_generic_open_id_fe = null; related_origins = null; feature_flag_continue_from_another_device = null; openid_configs = null; captcha_config = null; dummy_auth = null; register_rate_limit = null; }, )' | xxd -r -p | sha256sum ``` The output should match the argument hash.

• Proposal ID: 138376

  # Replace a node in subnet yinp6 Motivation: Having at least one node in a subnet per Node Provider Decentralization Nakamoto coefficient changes for subnet `yinp6-35cfo-wgcd2-oc4ty-2kqpf-t4dul-rfk33-fsq3r-mfmua-m2ngh-jqe`: ``` node_provider: 5.00 -> 5.00 (+0%) data_center: 5.00 -> 5.00 (+0%) data_center_owner: 5.00 -> 5.00 (+0%) area: 5.00 -> 4.00 (-20%) country: 5.00 -> 4.00 (-20%) ``` **Mean Nakamoto comparison:** 5.00 -> 4.67 (-7%) Overall replacement impact: (gets worse) the average log2 of Nakamoto Coefficients across all features decreases from 2.3219 to 2.2146 # Details Nodes removed: - `fxdqu-epq5z-kmnok-ch46f-jxujv-of7ws-3ec4b-gszap-gtklj-sxfiv-wae` [health: healthy] Nodes added: - `kow3e-amtig-nig34-yagqg-gvpq6-notwj-v4go3-3qnso-ysylr-7zdb4-mqe` [health: healthy] ``` node_provider data_center data_center_owner area country ------------- ----------- ----------------- ---- ------- 6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe 1 br1 1 -> 0 Africa Data Centres 1 Brussels Capital 1 -> 0 BE 1 -> 0 7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae 1 bu1 1 Central Tower DC 1 Bucuresti 1 CA 1 bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe 1 fr2 1 Cloud9 1 Gauteng 1 CH 1 -> 2 dhywe-eouw6-hstpj-ahsnw-xnjxq-cmqks-47mrg-nnncb-3sr5d-rac6m-nae 1 hu1 1 Cyxtera 1 Hesse 1 DE 1 i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae 1 jb2 1 Digital Realty 1 -> 0 Maribor 1 GE 1 ma7dp-gz4tg-3c2wv-pgnsv-wna7u-czvhu-fpu47-t4dr6-gzxql-wr2m2-qae 0 -> 1 kr1 1 Equinix 1 Navi Mumbai 1 IN 1 r3yjn-kthmg-pfgmb-2fngg-5c7d7-t6kqg-wi37r-j7gy6-iee64-kjdja-jae 1 mb1 1 Everyware 1 Ontario 1 KR 1 rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae 1 -> 0 nm1 1 Green.ch 0 -> 1 Seoul 1 PL 1 sqhxa-h6ili-qkwup-ohzwn-yofnm-vvnp5-kxdhg-saabw-rvua3-xp325-zqe 1 sg1 1 KT 1 Singapore 1 RO 1 ulyfm-vkxtj-o42dg-e4nam-l4tzf-37wci-ggntw-4ma7y-d267g-ywxi6-iae 1 tb1 1 M247 1 Tbilisi 1 SG 1 unqqg-no4b2-vbyad-ytik2-t3vly-3e57q-aje2t-sjb5l-bd4ke-chggn-uqe 1 to2 1 Posita.si 1 Texas 1 SI 1 vegae-c4chr-aetfj-7gzuh-c23sx-u2paz-vmvbn-bcage-pu7lu-mptnn-eqe 1 wa2 1 Rivram 1 Warszawa 1 US 1 wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae 1 zh2 1 TRG 1 Zurich 1 -> 2 ZA 1 wdnqm-clqti-im5yf-iapio-avjom-kyppl-xuiza-oaz6z-smmts-52wyg-5ae 1 zh5 0 -> 1 Telin 1 ```

• Proposal ID: 138375

  # Replace a node in subnet tdb26 Motivation: Replacing a dead node Decentralization Nakamoto coefficient changes for subnet `tdb26-jop6k-aogll-7ltgs-eruif-6kk7m-qpktf-gdiqx-mxtrf-vb5e6-eqe`: ``` node_provider: 12.00 -> 12.00 (+0%) data_center: 13.00 -> 13.00 (+0%) data_center_owner: 13.00 -> 13.00 (+0%) area: 7.00 -> 7.00 (+0%) country: 5.00 -> 5.00 (+0%) ``` **Mean Nakamoto comparison:** 10.50 -> 10.50 (+0%) Overall replacement impact: equal decentralization across all features # Details Nodes removed: - `daawl-5c7hb-iltb3-rkphn-d272x-kkpu4-vb5nr-4qxzp-azreg-47okd-gqe` [health: dead] Nodes added: - `4mfcc-d3te7-zk2in-n5hm2-tcquv-bgc2e-obpbh-xp5jc-7boqr-oidte-jqe` [health: healthy] ``` node_provider data_center data_center_owner area country ------------- ----------- ----------------- ---- ------- 4dibr-2alzr-h6kva-bvwn2-yqgsl-o577t-od46o-v275p-a2zov-tcw4f-eae 1 an1 1 Adam 1 Barcelona 1 AR 1 4jjya-hlyyc-s766p-fd6gr-d6tvv-vo3ah-j5ptx-i73gw-mwgyd-rw6w2-rae 1 ar1 1 Africa Data Centres 1 British Columbia 1 AU 1 64xe5-tx2s3-4gjmj-pnozr-fejw2-77y5y-rhcjk-glnmx-62brf-qin5q-pqe 1 bc1 1 Anonstake 1 Brussels Capital 1 BE 2 6nbcy-kprg6-ax3db-kh3cz-7jllk-oceyh-jznhs-riguq-fvk6z-6tsds-rqe 1 bn1 1 AtlasEdge 1 Bucuresti 1 CA 2 6sq7t-knkul-fko6h-xzvnf-ktbvr-jhx7r-hapzr-kjlek-whugy-zt6ip-xqe 1 br2 1 Baltneta 1 CABA 1 CH 3 7at4h-nhtvt-a4s55-jigss-wr2ha-ysxkn-e6w7x-7ggnm-qd3d5-ry66r-cae 1 bt1 1 CyrusOne 1 Cape Town 1 CZ 1 7ryes-jnj73-bsyu4-lo6h7-lbxk5-x4ien-lylws-5qwzl-hxd5f-xjh3w-mqe 1 bu1 1 Cyxtera 1 Colombo 1 ES 1 7uioy-xitfw-yqcko-5gpya-3lpsw-dw7zt-dyyyf-wfqif-jvi76-fdbkg-cqe 1 cm1 1 Datacenter United 1 Douglas 1 HK 2 acqus-l4yyc-h44lw-grfxw-h7jqf-mtvt3-huwmj-4s372-sc5db-5nsfr-2ae 1 ct2 1 Datasite 1 Flanders 1 IL 1 bvcsg-3od6r-jnydw-eysln-aql7w-td5zn-ay5m6-sibd2-jzojt-anwag-mqe 3 es1 1 Digital Realty 2 Florida 1 IM 1 cgmhq-c4zja-yov4u-zeyao-64ua5-idlhb-ezcgr-cultv-3vqjs-dhwo7-rqe 1 ge2 1 Edgoo Networks 1 Gauteng 2 IN 3 diyay-s4rfq-xnx23-zczwi-nptra-5254n-e4zn6-p7tqe-vqhzr-sd4gd-bqe 1 hk1 1 Equinix 1 Geneva 1 JP 1 efem5-kmwaw-xose7-zzhgg-6bfif-twmcw-csg7a-lmqvn-wrdou-mjwlb-vqe 1 hk4 1 Everyware 1 HongKong 2 KR 3 eybf4-6t6bb-unfb2-h2hhn-rrfi2-cd2vs-phksn-jdmbn-i463m-4lzds-vqe 1 hu1 1 Gasan 1 Lisbon 1 LK 1 g2ax6-jrkmb-3zuh3-jibtb-q5xoq-njrgo-5utbc-j2o7g-zfq2w-yyhky-dqe 1 im1 1 Interhost 1 Ljubljana 1 LT 1 i3cfo-s2tgu-qe5ym-wk7e6-y7ura-pptgu-kevuf-2feh7-z4enq-5hz4s-mqe 1 jb2 1 KT 1 London 1 LV 1 i7dto-bgkj2-xo5dx-cyrb7-zkk5y-q46eh-gz6iq-qkgyc-w4qte-scgtb-6ae 1 jb3 1 Latitude.sh 1 Maribor 1 PT 1 izmhk-lpjum-uo4oy-lviba-yctpc-arg4b-2ywim-vgoiu-gqaj2-gskmw-2qe 1 kr1 1 Leaseweb 1 Navi Mumbai 1 RO 1 kos24-5xact-6aror-uofg2-tnvt6-dq3bk-c2c5z-jtptt-jbqvc-lmegy-qae 1 kr2 1 M247 1 New Delhi 1 SE 2 mjnyf-lzqq6-s7fzb-62rqm-xzvge-5oa26-humwp-dvwxp-jxxkf-hoel7-fqe 1 ld1 1 Manx Telecom 1 Panvel 1 SG 2 mme7u-zxs3z-jq3un-fbaly-nllcz-toct2-l2kp3-larrb-gti4r-u2bmo-dae 1 li2 1 Marvelous Web3 DC 1 Quebec 1 SI 2 nmdd6-rouxw-55leh-wcbkn-kejit-njvje-p4s6e-v64d3-nlbjb-vipul-mae 1 lj2 1 Master Internet 1 Queensland 1 UK 1 pa5mu-yxsey-b4yrk-bodka-dhjnm-a3nx4-w2grw-3b766-ddr6e-nupu4-pqe 1 mb1 1 Megazone Cloud 1 Riga 1 US 3 py2kr-ipr2p-ryh66-x3a3v-5ts6u-7rfhf-alkna-ueffh-hz5ox-lt6du-qqe 1 mtl1 1 NEXTDC 1 Seoul 3 ZA 3 r3yjn-kthmg-pfgmb-2fngg-5c7d7-t6kqg-wi37r-j7gy6-iee64-kjdja-jae 1 nd1 1 Nano 1 Singapore 2 rbn2y-6vfsb-gv35j-4cyvy-pzbdu-e5aum-jzjg6-5b4n5-vuguf-ycubq-zae 1 nm1 1 Nine.Ch 1 South Moravian Region 1 rpfvr-s3kuw-xdqrr-pvuuj-hc7hl-olytw-yxlie-fmr74-sr572-6gdqx-iqe 1 or1 1 OrionStellar 1 Stockholm 2 s5nvr-ipdxf-xg6wd-ofacm-7tl4i-nwjzx-uulum-cugwb-kbpsa-wrsgs-cae 1 pl2 1 Posita.si 1 Tel Aviv 1 sixix-2nyqd-t2k2v-vlsyz-dssko-ls4hl-hyij4-y7mdp-ja6cj-nsmpf-yae 1 rg3 1 Racks Central 1 Texas 1 sqhxa-h6ili-qkwup-ohzwn-yofnm-vvnp5-kxdhg-saabw-rvua3-xp325-zqe 1 sc1 1 Rivram 1 Tokyo 1 ucjqj-jmbj3-rs4aq-ekzpw-ltjs3-zrcma-t6r3t-m5wxc-j5yrj-unwoj-mae 1 sg1 1 SafeHost 1 Vilnius 1 ulyfm-vkxtj-o42dg-e4nam-l4tzf-37wci-ggntw-4ma7y-d267g-ywxi6-iae 1 sg3 1 SyT - Servicios y Telecomunicaciones S.A. 1 Virginia 1 unqqg-no4b2-vbyad-ytik2-t3vly-3e57q-aje2t-sjb5l-bd4ke-chggn-uqe 1 sh1 2 TRG 1 Zurich 2 w4buy-lgwzr-pccs7-huzhh-qqnws-rns75-iaoox-jolrm-xs2ra-vdu3o-2qe 1 sl1 1 Telin 1 wdjjk-blh44-lxm74-ojj43-rvgf4-j5rie-nm6xs-xvnuv-j3ptn-25t4v-6ae 1 st1 1 Teraco 1 wwdbq-xuqhf-eydzu-oyl7p-ga565-zm7s7-yrive-ozgsy-zzgh3-qwb3j-cae 1 tv1 1 Unicom 1 x7uok-pi537-itm37-unjn3-ewkze-kuetg-kptap-nuqak-auq7z-tn5ey-dqe 1 ty3 1 Xneelo 1 zy4m7-z5mhs-zfkpl-zlsjl-blrbx-mvvmq-5z4zu-mf7eq-hhv7o-ezfro-3ae 1 zh2 1 Yotta 1 zh3 1 hkntt 1 ```

• Proposal ID: 138374

  # Publish SNS Swap WASM Built at Commit 0e4c823 __Proposer__: shahriar.javidi at dfinity.org __Source code__: [0e4c8234a9e0508ae30c5b8a7498406294c25e95][new-commit] [new-commit]: https://github.com/dfinity/ic/tree/0e4c8234a9e0508ae30c5b8a7498406294c25e95 ## Features & Fixes ### Changed * Expose a metric for whether auto finalization has failed. ## New Commits ``` $ git log --format="%C(auto) %h %s" 1377da9b6cec9d1b050864a44540311ae4be77d0..0e4c8234a9e0508ae30c5b8a7498406294c25e95 -- ./rs/sns/swap 4fd62f6e4b feat(swap): Expose a metric for whether auto finalization has failed (#6581) 186b42991d feat(sns): overwrite allowances (#6472) 43657c20bc feat(sns): use icrc-2 for the initialization of the SNS-Extensions (#6344) 49d659c29d feat: Unify ic-cdk to v0.18.6 (#6264) 6b037840af chore(nns/sns): Update changelogs for release (#6130) ``` ## Wasm 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/0e4c8234a9e0508ae30c5b8a7498406294c25e95/rs/nervous_system/docs/proposal_verification.md See ["Building the code"][prereqs] for prerequisites. [prereqs]: https://github.com/dfinity/ic/tree/0e4c8234a9e0508ae30c5b8a7498406294c25e95/README.adoc#building-the-code ``` # 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 0e4c8234a9e0508ae30c5b8a7498406294c25e95 # 2. Build canisters. ./ci/container/build-ic.sh -c # 3. Fingerprint the result. sha256sum ./artifacts/canisters/sns-swap-canister.wasm.gz ``` This should match `wasm` field of this proposal.

• Proposal ID: 138373

  # Publish SNS Governance WASM Built at Commit 0e4c823 __Proposer__: shahriar.javidi at dfinity.org __Source code__: [0e4c8234a9e0508ae30c5b8a7498406294c25e95][new-commit] [new-commit]: https://github.com/dfinity/ic/tree/0e4c8234a9e0508ae30c5b8a7498406294c25e95 ## Features & Fixes ### Added * Added `extension_operations` to `list_topics`, which exposes the operations of each registered extension underneath the topic which allows voters to correctly understand the impact of following on particular topics. Extensions are canisters that add additional functionality to an SNS through a privileged integration. ## New Commits ``` $ git log --format="%C(auto) %h %s" 6ab18899e82ac202fea4a549dcc6c5a5191e4992..0e4c8234a9e0508ae30c5b8a7498406294c25e95 -- ./rs/sns/governance 0e4c8234a9 chore(sns): revert rs/sns/governance/canister/canister.rs to state before 070bdf2 (#6631) e43fa2bbf9 feat(sns): Add v1 of kongswap adapter. (#6622) 070bdf267f chore(sns): Cleanup SNS migration code (#6599) d22dd09c6d fix(sns): approval fee added the by SNS approved value (#6593) 186b42991d feat(sns): overwrite allowances (#6472) ``` ## Wasm 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/0e4c8234a9e0508ae30c5b8a7498406294c25e95/rs/nervous_system/docs/proposal_verification.md See ["Building the code"][prereqs] for prerequisites. [prereqs]: https://github.com/dfinity/ic/tree/0e4c8234a9e0508ae30c5b8a7498406294c25e95/README.adoc#building-the-code ``` # 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 0e4c8234a9e0508ae30c5b8a7498406294c25e95 # 2. Build canisters. ./ci/container/build-ic.sh -c # 3. Fingerprint the result. sha256sum ./artifacts/canisters/sns-governance-canister.wasm.gz ``` This should match `wasm` field of this proposal.

• Proposal ID: 138372

  # Upgrade the Cycles-minting Canister to Commit 0e4c823 __Proposer__: shahriar.javidi at dfinity.org __Source code__: [0e4c8234a9e0508ae30c5b8a7498406294c25e95][new-commit] [new-commit]: https://github.com/dfinity/ic/tree/0e4c8234a9e0508ae30c5b8a7498406294c25e95 ## Features & Fixes ### Removed - Removed `transaction_notification` and `transaction_notification_pb` endpoints as they no longer be called. The ICP ledger removed the notify flow, and these methods were not callable by callers other than the ICP ledger. ## New Commits ``` $ git log --format="%C(auto) %h %s" 2407385056dbcd1d5eb15b84a9c0cd5f511ff997..0e4c8234a9e0508ae30c5b8a7498406294c25e95 -- ./rs/nns/cmc 138acf0ef3 chore(cmc): Remove unreachable functions (ledger removed notify flow) (#6575) 49d659c29d feat: Unify ic-cdk to v0.18.6 (#6264) 8cde73b3aa chore(nervous-system): Update changelog for release 2025-08-15 (#6300) ``` ## Upgrade Arguments ```candid () ``` ## Current Version __Current git hash__: 2407385056dbcd1d5eb15b84a9c0cd5f511ff997 __Current wasm hash__: ed459757dde6d88afc38e9034803b8774e850d584bf6292f15c1e28f579cc247 ## 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/0e4c8234a9e0508ae30c5b8a7498406294c25e95/rs/nervous_system/docs/proposal_verification.md ### WASM Verification See ["Building the code"][prereqs] for prerequisites. [prereqs]: https://github.com/dfinity/ic/tree/0e4c8234a9e0508ae30c5b8a7498406294c25e95/README.adoc#building-the-code ``` # 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 0e4c8234a9e0508ae30c5b8a7498406294c25e95 # 2. Build canisters. ./ci/container/build-ic.sh -c # 3. Fingerprint the result. sha256sum ./artifacts/canisters/cycles-minting-canister.wasm.gz ``` This should match `wasm_module_hash` field of this proposal. ### Upgrade Arguments Verification [`didc`][latest-didc] is required. [latest-didc]: https://github.com/dfinity/candid/releases/latest ``` didc encode '()' | xxd -r -p | sha256sum ``` This should match the `arg_hash` field of this proposal.

• Proposal ID: 138371

  # Upgrade the Registry Canister to Commit 0e4c823 __Proposer__: shahriar.javidi at dfinity.org __Source code__: [0e4c8234a9e0508ae30c5b8a7498406294c25e95][new-commit] [new-commit]: https://github.com/dfinity/ic/tree/0e4c8234a9e0508ae30c5b8a7498406294c25e95 ## Features & Fixes ### Added * New update method that will be used for node swapping feature. * `migrate_canisters` returns the new registry version. ## New Commits ``` $ git log --format="%C(auto) %h %s" abbed6b27a69f85f3ff539ed9a214faa666e1299..0e4c8234a9e0508ae30c5b8a7498406294c25e95 -- ./rs/registry/canister cef630e677 feat: Return registry version from `migrate_canisters` endpoint. (#6542) 4f9e7dcb8e feat: adding the data model and canister method for node swapping (#6487) c342b39ffe chore(nervous-system): Update changelog for release 2025-08-22 (#6411) 537b0fd653 feat(): Migrate Type0 and Type1 nodes to Type1dot1 (#6384) ``` ## Current Version __Current git hash__: abbed6b27a69f85f3ff539ed9a214faa666e1299 __Current wasm hash__: 45d28c292ce93744258bf904b107fcdf11a6bc8c87fa4dae04ab7131bc51ac3f ## 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/0e4c8234a9e0508ae30c5b8a7498406294c25e95/rs/nervous_system/docs/proposal_verification.md ### WASM Verification See ["Building the code"][prereqs] for prerequisites. [prereqs]: https://github.com/dfinity/ic/tree/0e4c8234a9e0508ae30c5b8a7498406294c25e95/README.adoc#building-the-code ``` # 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 0e4c8234a9e0508ae30c5b8a7498406294c25e95 # 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.

• Proposal ID: 138370

  # Upgrade the Sns-wasm Canister to Commit 0e4c823 __Proposer__: shahriar.javidi at dfinity.org __Source code__: [0e4c8234a9e0508ae30c5b8a7498406294c25e95][new-commit] [new-commit]: https://github.com/dfinity/ic/tree/0e4c8234a9e0508ae30c5b8a7498406294c25e95 ## Features & Fixes ### Added * A "/sns_canisters" HTTP endpoint for SNS canisters service discovery, used for prometheus. ## New Commits ``` $ git log --format="%C(auto) %h %s" 02571e8215fa3e77da791e693cc238b2de3beae9..0e4c8234a9e0508ae30c5b8a7498406294c25e95 -- ./rs/nns/sns-wasm ./rs/sns/init 8465248b4b feat(sns-wasm): Service discovery for SNS canisters (#6582) 49d659c29d feat: Unify ic-cdk to v0.18.6 (#6264) 758347643c feat(sns): add `Root.register_extension` (#5946) 3671acb49d chore: upgrade rust: 1.85.1 -> 1.86.0 (again) (#5453) b3efb00f64 docs(governance-backend): Update Governance backend CHANGELOG files. (#5450) ``` ## Current Version __Current git hash__: 02571e8215fa3e77da791e693cc238b2de3beae9 __Current wasm hash__: 2b3d631d7c158ef62d71e5f167535bc7f3fa48fe87301361c89f4f37458d60c1 ## 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/0e4c8234a9e0508ae30c5b8a7498406294c25e95/rs/nervous_system/docs/proposal_verification.md ### WASM Verification See ["Building the code"][prereqs] for prerequisites. [prereqs]: https://github.com/dfinity/ic/tree/0e4c8234a9e0508ae30c5b8a7498406294c25e95/README.adoc#building-the-code ``` # 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 0e4c8234a9e0508ae30c5b8a7498406294c25e95 # 2. Build canisters. ./ci/container/build-ic.sh -c # 3. Fingerprint the result. sha256sum ./artifacts/canisters/sns-wasm-canister.wasm.gz ``` This should match `wasm_module_hash` field of this proposal.

• Proposal ID: 138369

  # Upgrade the Governance Canister to Commit 0e4c823 __Proposer__: shahriar.javidi at dfinity.org __Source code__: [0e4c8234a9e0508ae30c5b8a7498406294c25e95][new-commit] [new-commit]: https://github.com/dfinity/ic/tree/0e4c8234a9e0508ae30c5b8a7498406294c25e95 ## Features & Fixes ### Added * The neuron `Split` command accepts an optional `memo` field that can be used to derive the neuron subaccount, rather than generating a random one. * The voting history of known neurons is recorded so that it can expose more information about the known neurons. ### Changed * The protobuf-encoded `Storable` implementations are changed to `Unbounded`. ### Removed * The `IcpXdrConversionRate` proposal is now obsolete and cannot be submitted. ## New Commits ``` $ git log --format="%C(auto) %h %s" 4b7cde9a0e3b5ad4725e75cbc36ce635be6fa6a8..0e4c8234a9e0508ae30c5b8a7498406294c25e95 -- ./rs/nns/governance ./rs/sns/init 01231e139f feat(nns): Record voting history of known neurons (#6531) 28a302d704 feat(nns): Change some NNS Governance storable types to Unbounded (#6603) 186b42991d feat(sns): overwrite allowances (#6472) 8c112462b8 feat(nns): Add memo for the split neuron command (#6499) 43657c20bc feat(sns): use icrc-2 for the initialization of the SNS-Extensions (#6344) 49d659c29d feat: Unify ic-cdk to v0.18.6 (#6264) d8fb1363ef refactor(nns): Make ExchangeRate proposals obsolete (#5172) 2f27cecce0 doc(nns): Say that Topic.TOPIC_UNSPECIFIED is not applicable to Governance/SNS/Neuron's fund (#6328) c0a60bb5ea feat: bootstrap NNS governance and root canisters (#6254) a4c1c9bce1 chore: update rust to 1.88.0 (#6045) af7da00221 chore(nervous-system): Update changelog for release 2025-07-30 (#6113) ``` ## Current Version __Current git hash__: 4b7cde9a0e3b5ad4725e75cbc36ce635be6fa6a8 __Current wasm hash__: e774351d97bf02469a7c469264be533b3696d21930fc11e9e5cb87a747813aa1 ## 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/0e4c8234a9e0508ae30c5b8a7498406294c25e95/rs/nervous_system/docs/proposal_verification.md ### WASM Verification See ["Building the code"][prereqs] for prerequisites. [prereqs]: https://github.com/dfinity/ic/tree/0e4c8234a9e0508ae30c5b8a7498406294c25e95/README.adoc#building-the-code ``` # 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 0e4c8234a9e0508ae30c5b8a7498406294c25e95 # 2. Build canisters. ./ci/container/build-ic.sh -c # 3. Fingerprint the result. sha256sum ./artifacts/canisters/governance-canister.wasm.gz ``` This should match `wasm_module_hash` field of this proposal.

• Proposal ID: 138368

  Update subnet xlkub-3thlm-uha3c-hqmfw-qykp5-6rldi-hpfxy-nwyxy-w6bbk-tpg5h-vqe to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138367

  Update subnet rtvil-s5u5d-jbj7o-prlhw-bzlr5-3j5kn-2iu7a-jq2hl-avkhn-w7oa7-6ae to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138366

  # Upgrade frontend NNS Dapp canister to commit `e91bdc380d234ed4060f63d50fafe4bbfeda9c70` Wasm sha256 hash: `6555d1b3bd8f0ec9e3be3a7e30a5ecee2650c4d8f2a2b2c766db7af4d499be75` (`https://github.com/dfinity/nns-dapp/actions/runs/17461489580`) ## Change Log ### Changed * Chain-key tokens sorting. * Changed Project's card stat Market Cap to Fully Diluted Valuation. ### Fixed * Remove extra character from a Project's page details. * Upgrate AgentJS to fix canister management issues. ## Commit Log ``` + bash -xc "git log --format='%C(auto) %h %s' ae8fcd4f1..e91bdc380" e91bdc380 Update ckToken sorting (#7322) a994ff3ae bot: Update SNS Aggregator Response (#7327) 69167c542 fix(aggregator): handle new InfoTopic extension field (#7324) 1620fa027 bot: Update proposals candid bindings (#7325) 5126b011a bot: Update sns_aggregator candid bindings (#7318) 4e9542821 feat(projects): replace market cap with FDV metric (#7320) 86b7fee77 feat(config): disable CK tokens through feature flag (#7315) 7dffdf4f3 fix: canisters mgmt calls failing with aaaaa-aa not in ranges field (#7321) d78c186e2 Update changelog after release (#7316) 9bb117406 fix(ui): remove extra character from a Project's page details (#7317) 00b1abf58 feat: Remove SnsAggregator.stable_data as the function is broken in production and no longer used in testing (#7295) a77f06c47 fix(deps): update gix for markdown SVG rendering (#7313) b7ab63a84 bot: Update snsdemo to release-2025-08-27 (#7311) 989e1830c bot: Update SNS Aggregator Response (#7310) 8431d9666 bot: Bump gix-components (#7282) c9200e75c fix(sns_aggregator): ensure last page exists (#7312) ``` ## Wasm Verification To build the wasm module yourself and verify its hash, run the following commands from the root of the [nns-dapp repo](https://github.com/dfinity/nns-dapp): ``` git fetch # to ensure you have the latest changes. git checkout "e91bdc380d234ed4060f63d50fafe4bbfeda9c70" git merge-base --is-ancestor HEAD origin/main && echo "OK" || echo "Commit is not on main branch!" ./scripts/docker-build sha256sum nns-dapp.wasm.gz ``` You may also want to verify the canister arguments. In the proposal they are binary, which is not very readable. Docker provides both binary and text formats and you can verify that the text format corresponds to the binary `arg_hash` field in the proposal. ``` cat nns-dapp-arg-mainnet.did didc encode "$(cat nns-dapp-arg-mainnet.did)" | xxd -r -p | sha256sum ```

• Proposal ID: 138365

  Register a node provider 'achermann.swiss', in line with the announcement and discussion at https://forum.dfinity.org/t/swiss-subnet-node-provider-onboarding-has-begun/55556/112. All documents below and their hashes are available on the IC Wiki (https://wiki.internetcomputer.org/wiki/Achermann.swiss). * Identity and Compliance Declaration: d37d0527a7e5904739063071c2a188a23f137701270f2163193cd16fe1d7214c * Assessment of Independence: 6fbe2c70e5f68842a9702ea320fc2d13df90101dd506781e4777926559b491ed * Proof of Identity: 4b48cd2ec5852924511ee37709501eeb467383ab47f9948de4764519e246132a

• Proposal ID: 138364

  Release Notes for [**release-2025-09-04\_03-11-base**](https://github.com/dfinity/ic/tree/release-2025-09-04_03-11-base) (9152ba15ab6cc3c12eb407e13f8ee483a1d5723c) =================================================================================================================================================================== This release is based on changes since [release-2025-08-28\_03-17-base](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12) (84a268e93a909a6827d76ad794411b161c839a12). Please note that some commits may be excluded from this release if they're not relevant, or not modifying the HostOS image. Additionally, descriptions of some changes might have been slightly modified to fit the release notes format. To see a full list of commits added since last release, compare the revisions on [GitHub](https://github.com/dfinity/ic/compare/release-2025-08-28_03-17-base...release-2025-09-04_03-11-base). Features: --------- * [`bbf3a56ce`](https://github.com/dfinity/ic/commit/bbf3a56ce) Interface,Node(node): generate-ic-config follow ups ([#6471](https://github.com/dfinity/ic/pull/6471)) Chores: ------- * [`f0bfdd2c8`](https://github.com/dfinity/ic/commit/f0bfdd2c8) Interface,Node: Factor out VSockClient trait ([#6523](https://github.com/dfinity/ic/pull/6523)) * [`be7421c09`](https://github.com/dfinity/ic/commit/be7421c09) Owners: bump tracing-subscriber to 0.3.20 ([#6585](https://github.com/dfinity/ic/pull/6585)) * [`29441688a`](https://github.com/dfinity/ic/commit/29441688a) Node: Update Base Image Refs [2025-08-28-0805] ([#6503](https://github.com/dfinity/ic/pull/6503)) Refactoring: ------------ * [`ac630a3fe`](https://github.com/dfinity/ic/commit/ac630a3fe) Interface,Node: Move fetching SEV certs higher up in the call stack ([#6522](https://github.com/dfinity/ic/pull/6522)) ------------------------------------------ Full list of changes (including the ones that are not relevant to HostOS) can be found on [GitHub](https://github.com/dfinity/dre/blob/9b43cbb16bff45fb4f7be27e51036945272e7498/hostos-releases/9152ba15ab6cc3c12eb407e13f8ee483a1d5723c.md). # IC-OS Verification To build and verify the IC-OS HostOS disk image, after installing curl if necessary (`sudo apt install curl`), run: ``` # From https://github.com/dfinity/ic#verifying-releases curl -fsSL https://raw.githubusercontent.com/dfinity/ic/master/ci/tools/repro-check | python3 - -c 9152ba15ab6cc3c12eb407e13f8ee483a1d5723c --hostos ``` The two SHA256 sums printed above from a) the downloaded CDN image and b) the locally built image, must be identical, and must match the SHA256 from the payload of the NNS proposal. While not required for this NNS proposal, as we are only electing a new HostOS version here, you have the option to verify the build reproducibility of the GuestOS by passing `--guestos` to the script above instead of `--hostos`, or the SetupOS by passing `--setupos`.

• Proposal ID: 138363

  Release Notes for [release-2025-09-04\_03-11-inmem-canister-sks](https://github.com/dfinity/ic/tree/release-2025-09-04_03-11-inmem-canister-sks) (`ab62c6ec1c3b5f492df53c05bb0bf5f2eb6298ba`) ============================================================================================================================================================================================= This release is based on changes since [release-2025-09-04\_03-11-base](https://dashboard.internetcomputer.org/release/9152ba15ab6cc3c12eb407e13f8ee483a1d5723c) (`9152ba15ab6cc3c12eb407e13f8ee483a1d5723c`). Please note that some commits may be excluded from this release if they're not relevant, or not modifying the GuestOS image. Additionally, descriptions of some changes might have been slightly modified to fit the release notes format. To see a full list of commits added since last release, compare the revisions on [GitHub](https://github.com/dfinity/ic/compare/release-2025-09-04_03-11-base...release-2025-09-04_03-11-inmem-canister-sks). Features: --------- * [`ab62c6ec1`](https://github.com/dfinity/ic/commit/ab62c6ec1) Crypto,Interface(crypto): in-memory canister secret key store # IC-OS Verification To build and verify the IC-OS GuestOS disk image, after installing curl if necessary (`sudo apt install curl`), run: ``` # From https://github.com/dfinity/ic#verifying-releases curl -fsSL https://raw.githubusercontent.com/dfinity/ic/master/ci/tools/repro-check | python3 - -c ab62c6ec1c3b5f492df53c05bb0bf5f2eb6298ba --guestos ``` The two SHA256 sums printed above from a) the downloaded CDN image and b) the locally built image, must be identical, and must match the SHA256 from the payload of the NNS proposal. While not required for this NNS proposal, as we are only electing a new GuestOS version here, you have the option to verify the build reproducibility of the HostOS by passing `--hostos` to the script above instead of `--guestos`, or the SetupOS by passing `--setupos`.

• Proposal ID: 138362

  Release Notes for [release-2025-09-04\_03-11-snapshot-downloads](https://github.com/dfinity/ic/tree/release-2025-09-04_03-11-snapshot-downloads) (`c6d90cb33f3d47f808aaaf227a1678cb812d74a2`) ============================================================================================================================================================================================= This release is based on changes since [release-2025-09-04\_03-11-base](https://dashboard.internetcomputer.org/release/9152ba15ab6cc3c12eb407e13f8ee483a1d5723c) (`9152ba15ab6cc3c12eb407e13f8ee483a1d5723c`). Please note that some commits may be excluded from this release if they're not relevant, or not modifying the GuestOS image. Additionally, descriptions of some changes might have been slightly modified to fit the release notes format. To see a full list of commits added since last release, compare the revisions on [GitHub](https://github.com/dfinity/ic/compare/release-2025-09-04_03-11-base...release-2025-09-04_03-11-snapshot-downloads). Other changes: -------------- * [`c6d90cb33`](https://github.com/dfinity/ic/commit/c6d90cb33) Execution,Interface: turn on feature flag for canister snapshot download and upload # IC-OS Verification To build and verify the IC-OS GuestOS disk image, after installing curl if necessary (`sudo apt install curl`), run: ``` # From https://github.com/dfinity/ic#verifying-releases curl -fsSL https://raw.githubusercontent.com/dfinity/ic/master/ci/tools/repro-check | python3 - -c c6d90cb33f3d47f808aaaf227a1678cb812d74a2 --guestos ``` The two SHA256 sums printed above from a) the downloaded CDN image and b) the locally built image, must be identical, and must match the SHA256 from the payload of the NNS proposal. While not required for this NNS proposal, as we are only electing a new GuestOS version here, you have the option to verify the build reproducibility of the HostOS by passing `--hostos` to the script above instead of `--guestos`, or the SetupOS by passing `--setupos`.

• Proposal ID: 138361

  Release Notes for [release-2025-09-04\_03-11-base](https://github.com/dfinity/ic/tree/release-2025-09-04_03-11-base) (`9152ba15ab6cc3c12eb407e13f8ee483a1d5723c`) ================================================================================================================================================================= This release is based on changes since [release-2025-08-28\_03-17-base](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12) (`84a268e93a909a6827d76ad794411b161c839a12`). Please note that some commits may be excluded from this release if they're not relevant, or not modifying the GuestOS image. Additionally, descriptions of some changes might have been slightly modified to fit the release notes format. To see a full list of commits added since last release, compare the revisions on [GitHub](https://github.com/dfinity/ic/compare/release-2025-08-28_03-17-base...release-2025-09-04_03-11-base). Features: --------- * [`d936be769`](https://github.com/dfinity/ic/commit/d936be769) Consensus,Execution,Interface(XC): enable Dogecoin for staging canisters ([#6563](https://github.com/dfinity/ic/pull/6563)) * [`343c6fc03`](https://github.com/dfinity/ic/commit/343c6fc03) Consensus,Interface: Start the creation of new pre-signatures for the emptiest stash ([#6477](https://github.com/dfinity/ic/pull/6477)) * [`69b755062`](https://github.com/dfinity/ic/commit/69b755062) Consensus,Interface(btc-adapter): remove dependency on bitcoincore-rpc ([#6412](https://github.com/dfinity/ic/pull/6412)) * [`44b1fc97b`](https://github.com/dfinity/ic/commit/44b1fc97b) Consensus,Interface: Start IDkgBlockReader above certified height during payload creation & validation ([#6308](https://github.com/dfinity/ic/pull/6308)) * [`464301da9`](https://github.com/dfinity/ic/commit/464301da9) Execution,Interface: Purge pre-signatures that exceed the maximum stash size ([#6504](https://github.com/dfinity/ic/pull/6504)) * [`039a1acf9`](https://github.com/dfinity/ic/commit/039a1acf9) Interface: adding ic-admin calls to swap node in subnet directly ([#6550](https://github.com/dfinity/ic/pull/6550)) * [`28de7a00e`](https://github.com/dfinity/ic/commit/28de7a00e) Interface(ICRC-Archive): Ensure upgrade u64 <-> u256 fails ([#6546](https://github.com/dfinity/ic/pull/6546)) * [`4f9e7dcb8`](https://github.com/dfinity/ic/commit/4f9e7dcb8) Interface: adding the data model and canister method for node swapping ([#6487](https://github.com/dfinity/ic/pull/6487)) * [`e3857ed56`](https://github.com/dfinity/ic/commit/e3857ed56) Interface(ICRC-Ledger): Ensure upgrade u64 <-> u256 fails ([#6486](https://github.com/dfinity/ic/pull/6486)) * [`4b0d3410f`](https://github.com/dfinity/ic/commit/4b0d3410f) Interface,Message Routing: Reject requests coming from seemly wrong subnet ([#6480](https://github.com/dfinity/ic/pull/6480)) * [`55fb2f974`](https://github.com/dfinity/ic/commit/55fb2f974) Interface,Message Routing: allow requests to arrive to migrated-away canister ([#6430](https://github.com/dfinity/ic/pull/6430)) * [`c4ab3bf04`](https://github.com/dfinity/ic/commit/c4ab3bf04) Interface,Message Routing: Soft limit for merge size ([#6475](https://github.com/dfinity/ic/pull/6475)) * [`6ab18899e`](https://github.com/dfinity/ic/commit/6ab18899e) Interface,Node: Attestation crate ([#6467](https://github.com/dfinity/ic/pull/6467)) * [`bbf3a56ce`](https://github.com/dfinity/ic/commit/bbf3a56ce) Interface,Node(node): generate-ic-config follow ups ([#6471](https://github.com/dfinity/ic/pull/6471)) Bugfixes: --------- * [`7e6022cd1`](https://github.com/dfinity/ic/commit/7e6022cd1) Consensus,Interface: Use correct registry version for `ChainKeyConfig` in IDKG data payload builder ([#6565](https://github.com/dfinity/ic/pull/6565)) * [`e35448e99`](https://github.com/dfinity/ic/commit/e35448e99) Consensus,Interface(orchestrator): Introduce timeout with backoff when fetching CUPs ([#6219](https://github.com/dfinity/ic/pull/6219)) Performance improvements: ------------------------- * [`0851642d9`](https://github.com/dfinity/ic/commit/0851642d9) Consensus,Interface(idkg): reduce the number of support share validations ([#6526](https://github.com/dfinity/ic/pull/6526)) Chores: ------- * [`9e79433b4`](https://github.com/dfinity/ic/commit/9e79433b4) Consensus,Interface: Add a topology version metric and use it in some tests adding nodes ([#6574](https://github.com/dfinity/ic/pull/6574)) * [`c6fc12aec`](https://github.com/dfinity/ic/commit/c6fc12aec) Consensus,Interface: open FW for SOCKS proxy port for system or app subnet nodes ([#6511](https://github.com/dfinity/ic/pull/6511)) * [`324a36643`](https://github.com/dfinity/ic/commit/324a36643) Consensus,Interface(canister\_migration): Rename some structs/constants from *CALL\_V3* to *SYNC\_CALL* ([#6492](https://github.com/dfinity/ic/pull/6492)) * [`4c5147ff0`](https://github.com/dfinity/ic/commit/4c5147ff0) Crypto: use ic-principal instead of full candid ([#6352](https://github.com/dfinity/ic/pull/6352)) * [`c0f4416b7`](https://github.com/dfinity/ic/commit/c0f4416b7) Crypto,Interface,Message Routing: Add exclusive filtering to MixedHashTree ([#6566](https://github.com/dfinity/ic/pull/6566)) * [`31e3a6e90`](https://github.com/dfinity/ic/commit/31e3a6e90) Execution,Interface: Inline execution dependencies ([#6579](https://github.com/dfinity/ic/pull/6579)) * [`d26ef1fe5`](https://github.com/dfinity/ic/commit/d26ef1fe5) Execution,Interface(fuzzing): Make sandbox binary identifiable via a custom section ([#6568](https://github.com/dfinity/ic/pull/6568)) * [`04affbae7`](https://github.com/dfinity/ic/commit/04affbae7) Execution,Interface: Use `HeapBytes` in caches ([#6445](https://github.com/dfinity/ic/pull/6445)) * [`c6b33304a`](https://github.com/dfinity/ic/commit/c6b33304a) Interface: use PocketIcBuilder::with\_all\_icp\_features in sns-testing ([#6474](https://github.com/dfinity/ic/pull/6474)) * [`a24b7d484`](https://github.com/dfinity/ic/commit/a24b7d484) Interface: remove drun from IC repo ([#6535](https://github.com/dfinity/ic/pull/6535)) * [`00c309a20`](https://github.com/dfinity/ic/commit/00c309a20) Interface: Stop preparing routing table in the old format outside of production ([#6059](https://github.com/dfinity/ic/pull/6059)) * [`4283ad61c`](https://github.com/dfinity/ic/commit/4283ad61c) Interface,Message Routing: state sync cache should not be updated by another one in Prep phase ([#6580](https://github.com/dfinity/ic/pull/6580)) * [`8d3a745a8`](https://github.com/dfinity/ic/commit/8d3a745a8) Interface,Message Routing: Remove Certification Versions below V19 ([#6427](https://github.com/dfinity/ic/pull/6427)) * [`f0bfdd2c8`](https://github.com/dfinity/ic/commit/f0bfdd2c8) Interface,Node: Factor out VSockClient trait ([#6523](https://github.com/dfinity/ic/pull/6523)) * [`be7421c09`](https://github.com/dfinity/ic/commit/be7421c09) Owners: bump tracing-subscriber to 0.3.20 ([#6585](https://github.com/dfinity/ic/pull/6585)) * [`29441688a`](https://github.com/dfinity/ic/commit/29441688a) Node: Update Base Image Refs [2025-08-28-0805] ([#6503](https://github.com/dfinity/ic/pull/6503)) Refactoring: ------------ * [`ac630a3fe`](https://github.com/dfinity/ic/commit/ac630a3fe) Interface,Node: Move fetching SEV certs higher up in the call stack ([#6522](https://github.com/dfinity/ic/pull/6522)) Tests: ------ * [`504f6795a`](https://github.com/dfinity/ic/commit/504f6795a) Interface,Node(doge): dogecoin adapter system tests ([#6414](https://github.com/dfinity/ic/pull/6414)) --------------------------------------- Full list of changes (including the ones that are not relevant to GuestOS) can be found on [GitHub](https://github.com/dfinity/dre/blob/c6844a8e4bc8bed57bc8fe9a4692234b3a9872bf/replica-releases/9152ba15ab6cc3c12eb407e13f8ee483a1d5723c.md). # IC-OS Verification To build and verify the IC-OS GuestOS disk image, after installing curl if necessary (`sudo apt install curl`), run: ``` # From https://github.com/dfinity/ic#verifying-releases curl -fsSL https://raw.githubusercontent.com/dfinity/ic/master/ci/tools/repro-check | python3 - -c 9152ba15ab6cc3c12eb407e13f8ee483a1d5723c --guestos ``` The two SHA256 sums printed above from a) the downloaded CDN image and b) the locally built image, must be identical, and must match the SHA256 from the payload of the NNS proposal. While not required for this NNS proposal, as we are only electing a new GuestOS version here, you have the option to verify the build reproducibility of the HostOS by passing `--hostos` to the script above instead of `--guestos`, or the SetupOS by passing `--setupos`.

• Proposal ID: 138360

  Register a node provider 'LTIN AG', in line with the announcement and discussion at https://forum.dfinity.org/t/swiss-subnet-node-provider-onboarding-has-begun/55556/121. All documents below and their hashes are available on the IC Wiki (https://wiki.internetcomputer.org/wiki/LTIN_AG). * Identity and Compliance Declaration: e05e0328cea770524b8cd227ce2fe12a002c9f5b54abb404724e722fac444cce * Assessment of Independence: 54966ca6fde96b2e81df6089890050e48f294ffba76705d8f388a13544d1644d * Proof of Identity: cf172c903810162baffe80ecfac02ed947322e6d013bf141c3ef4c693b2f829f

• Proposal ID: 138359

  Allow the principal `mf7xa-laaaa-aaaar-qaaaa-cai`, which is a DFINITY-controlled wallet, to create canisters on the Bitcoin subnet ([w4rem](https://dashboard.internetcomputer.org/network/subnets/w4rem-dv5e3-widiz-wbpea-kbttk-mnzfm-tzrc7-svcj3-kbxyb-zamch-hqe)) in preparation for the native Dogecoin integration needed for the [Meridian milestone](https://internetcomputer.org/roadmap#Chain%20Fusion-Meridian).

• Proposal ID: 138358

  Update subnet nl6hn-ja4yw-wvmpy-3z2jx-ymc34-pisx3-3cp5z-3oj4a-qzzny-jbsv3-4qe to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138357

  Update subnet pzp6e-ekpqk-3c5x7-2h6so-njoeq-mt45d-h3h6c-q3mxf-vpeq5-fk5o7-yae to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138356

  Update subnet 3hhby-wmtmw-umt4t-7ieyg-bbiig-xiylg-sblrt-voxgt-bqckd-a75bf-rqe to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138355

  Register a node provider 'Blockchain Innovation Group', in line with the announcement and discussion at https://forum.dfinity.org/t/swiss-subnet-node-provider-onboarding-has-begun/55556/118. All documents below and their hashes are available on the IC Wiki (https://wiki.internetcomputer.org/wiki/Blockchain_Innovation_Group). * Identity and Compliance Declaration: e4dadc7ee8f1ca0096f4dce92be1d21e87167930a9aa1f1967f101dd8ded40d6 * Assessment of Independence: 4e552bcbfb5f9f738250a76839dd47fd7738cebe75e9cf629313623ff3f14be5 * Proof of Identity: 40c5e66fc74d585845cf6b38d75f68549b3d96b1fea1d6219aa570affbc31082

• Proposal ID: 138354

  Update subnet mpubz-g52jc-grhjo-5oze5-qcj74-sex34-omprz-ivnsm-qvvhr-rfzpv-vae to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138353

  Update subnet gmq5v-hbozq-uui6y-o55wc-ihop3-562wb-3qspg-nnijg-npqp5-he3cj-3ae to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138352

  Update subnet x33ed-h457x-bsgyx-oqxqf-6pzwv-wkhzr-rm2j3-npodi-purzm-n66cg-gae to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138351

  Update subnet jtdsg-3h6gi-hs7o5-z2soi-43w3z-soyl3-ajnp3-ekni5-sw553-5kw67-nqe to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138350

  Update subnet yinp6-35cfo-wgcd2-oc4ty-2kqpf-t4dul-rfk33-fsq3r-mfmua-m2ngh-jqe to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138349

  Update subnet bkfrj-6k62g-dycql-7h53p-atvkj-zg4to-gaogh-netha-ptybj-ntsgw-rqe to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138348

  Update subnet 6pbhf-qzpdk-kuqbr-pklfa-5ehhf-jfjps-zsj6q-57nrl-kzhpd-mu7hc-vae to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138347

  Update subnet e66qm-3cydn-nkf4i-ml4rb-4ro6o-srm5s-x5hwq-hnprz-3meqp-s7vks-5qe to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138346

  Update subnet w4rem-dv5e3-widiz-wbpea-kbttk-mnzfm-tzrc7-svcj3-kbxyb-zamch-hqe to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138345

  Update API boundary nodes to GuestOS version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12) Motivation: update the API boundary nodes yqbqe-whgvn-teyic-zvtln-rcolf-yztin-ecal6-smlwy-6imph-6isdn-qqe.

• Proposal ID: 138344

  Update API boundary nodes to GuestOS version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12) Motivation: update the API boundary nodes upg5h-ggk5u-6qxp7-ksz3r-osynn-z2wou-65klx-cuala-sd6y3-3lorr-dae.

• Proposal ID: 138343

  Update API boundary nodes to GuestOS version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12) Motivation: update the API boundary nodes ubipk-gibrt-gr23n-u4mrg-iwgaa-4jz42-y6gt6-3htxw-3mq2m-dwhv2-pqe.

• Proposal ID: 138342

  Update subnet 2zs4v-uoqha-xsuun-lveyr-i4ktc-5y3ju-aysud-niobd-gxnqa-ctqem-hae to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138341

  Update subnet kp5jj-kpgmn-f4ohx-uqot6-wtbbr-lmtqv-kpkaf-gcksv-snkwm-43kmy-iae to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138340

  Update subnet 6excn-doq5g-bmrxd-3774i-hjnn2-3ovbo-xjwz7-3yozt-fsbzx-bethy-bae to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138339

  Update API boundary nodes to GuestOS version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12) Motivation: update the API boundary nodes q6hk7-hplmv-xsedz-5bv7n-vfkws-rjyel-ijhge-hx2zg-nk7wb-tzisp-xqe.

• Proposal ID: 138338

  Update API boundary nodes to GuestOS version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12) Motivation: update the API boundary nodes pxxcj-h2sa5-q2yql-4j7od-jwtvq-uisnw-w2ox6-xtfqi-noxva-nlgxx-wqe.

• Proposal ID: 138337

  Update API boundary nodes to GuestOS version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12) Motivation: update the API boundary nodes mj4qw-5oxqx-5jgpn-66re3-gzgjb-rphz5-hmwhc-ahaa5-vespc-s4maj-vqe.

• Proposal ID: 138336

  Update API boundary nodes to GuestOS version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12) Motivation: update the API boundary nodes mbsyf-dtlsd-ccjq4-63rmh-u2lv7-dwxuq-ym6bk-63i2l-5uyki-zccek-mqe.

• Proposal ID: 138335

  Update subnet lspz2-jx4pu-k3e7p-znm7j-q4yum-ork6e-6w4q6-pijwq-znehu-4jabe-kqe to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138334

  Update subnet o3ow2-2ipam-6fcjo-3j5vt-fzbge-2g7my-5fz2m-p4o2t-dwlc4-gt2q7-5ae to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138333

  Update subnet opn46-zyspe-hhmyp-4zu6u-7sbrh-dok77-m7dch-im62f-vyimr-a3n2c-4ae to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138332

  Update API boundary nodes to GuestOS version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12) Motivation: update the API boundary nodes lwxeh-xayoz-wu5eb-hwraj-a3pew-yeioj-cnwat-5uow4-ugxkc-kx44o-4ae.

• Proposal ID: 138331

  Update API boundary nodes to GuestOS version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12) Motivation: update the API boundary nodes jlifv-mddo3-zfwdc-x2wmu-xklbj-dai3i-3pvjy-j4hqm-sarqr-fhkq6-zae.

• Proposal ID: 138330

  Update API boundary nodes to GuestOS version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12) Motivation: update the API boundary nodes gvqb5-b2623-3twpd-mruy4-3grts-agp2t-wgmt4-hspvj-5oyl6-kje32-aqe.

• Proposal ID: 138329

  Update API boundary nodes to GuestOS version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12) Motivation: update the API boundary nodes ek6px-kxr47-noli7-nyjql-au5uc-tmj3k-777mf-lfla5-k4xx4-msu3j-dae.

• Proposal ID: 138328

  Update subnet cv73p-6v7zi-u67oy-7jc3h-qspsz-g5lrj-4fn7k-xrax3-thek2-sl46v-jae to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138327

  Update subnet 4ecnw-byqwz-dtgss-ua2mh-pfvs7-c3lct-gtf4e-hnu75-j7eek-iifqm-sqe to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138326

  Update subnet k44fs-gm4pv-afozh-rs7zw-cg32n-u7xov-xqyx3-2pw5q-eucnu-cosd4-uqe to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138325

  Update API boundary nodes to GuestOS version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12) Motivation: update the API boundary nodes ec62l-q44va-5lyw2-gbl4w-xcx55-c3qv4-q67vc-fu6s7-xpm2r-7tjrw-tae.

• Proposal ID: 138324

  Update API boundary nodes to GuestOS version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12) Motivation: update the API boundary nodes dl74z-6vpps-k6bpu-5hjsj-fb6lb-34tsv-ue5gt-bdkjn-35pt5-fdu2a-rae.

• Proposal ID: 138323

  Update API boundary nodes to GuestOS version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12) Motivation: update the API boundary nodes coqzx-lgyi2-hizw4-nax6t-mshs6-y4ml6-xon24-ioon4-rer4r-qtuan-cae.

• Proposal ID: 138322

  Update API boundary nodes to GuestOS version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12) Motivation: update the API boundary nodes bfj6y-cmhcf-6fxs7-ku2u4-tucww-b2eej-2dmap-snurk-3yaks-ss7xe-rae.

• Proposal ID: 138321

  Update API boundary nodes to GuestOS version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12) Motivation: update the API boundary nodes bcbz4-w2ogq-jt7xk-xd7b2-ylhei-ygp3n-pjpdy-253tu-fpn3s-f5asy-fqe.

• Proposal ID: 138320

  Update subnet brlsh-zidhj-3yy3e-6vqbz-7xnih-xeq2l-as5oc-g32c4-i5pdn-2wwof-oae to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138319

  Update subnet eq6en-6jqla-fbu5s-daskr-h6hx2-376n5-iqabl-qgrng-gfqmv-n3yjr-mqe to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138318

  Update subnet lhg73-sax6z-2zank-6oer2-575lz-zgbxx-ptudx-5korm-fy7we-kh4hl-pqe to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138317

  Update API boundary nodes to GuestOS version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12) Motivation: update the API boundary nodes atrq6-prjsa-w2b32-gyukj-ivjd6-kc4gq-ufi6v-yier6-puxtx-n2ipp-fqe.

• Proposal ID: 138316

  Node provider 'NOKU SA' is adding 1 node in the ti1 data center. See links below for more information: * Subnet rental request: https://dashboard.internetcomputer.org/proposal/136408 * Swiss Subnet Introduction: https://forum.dfinity.org/t/introducing-the-swiss-subnet-a-secure-and-compliant-blockchain-infrastructure-leveraging-the-internet-computer-protocol/41135 * Swiss Subnet Node Provider Onboarding: https://forum.dfinity.org/t/swiss-subnet-node-provider-onboarding-has-begun/55556 , https://forum.dfinity.org/t/swiss-subnet-node-provider-onboarding-has-begun/55556/104 Additional documents: * Self Declaration Documents on IC Wiki: https://wiki.internetcomputer.org/wiki/NOKU_SA * Forum post: https://forum.dfinity.org/t/swiss-subnet-node-provider-onboarding-has-begun/55556/21

• Proposal ID: 138315

  Update API boundary nodes to GuestOS version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12) Motivation: update the API boundary nodes 5dpkp-lfhr2-j7mfz-gavpn-puej5-wdfzg-fw42o-zupnu-izvk3-ubzzi-6ae.

• Proposal ID: 138314

  Register a node provider 'CoreLedger', in line with the announcement and discussion at https://forum.dfinity.org/t/swiss-subnet-node-provider-onboarding-has-begun/55556/47. All documents below and their hashes are available on the IC Wiki (https://wiki.internetcomputer.org/wiki/CoreLedger). * Identity and Compliance Declaration: 1888807214277f9566a3245fe36909f7f5e7da311fbed1ab7bd5669f73a4e46e * Independence Assessment: b2750cfd99ac8b3ea3055daa1af7732d78a6be1c752496b6fea960f2da064b7e * Proof of Identity: e8b375a64143957dd1b391198e7a618f48baead034186f2c18d27fb26a2d30c2

• Proposal ID: 138313

  Update API boundary nodes to GuestOS version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12) Motivation: update the API boundary nodes 4p3lu-7sy3a-ph47t-wlvb6-naehi-oki2f-pkokv-hovam-s5iul-sxvwk-3ae.

• Proposal ID: 138312

  Update subnet pae4o-o6dxf-xki7q-ezclx-znyd6-fnk6w-vkv5z-5lfwh-xym2i-otrrw-fqe to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138311

  Update subnet csyj4-zmann-ys6ge-3kzi6-onexi-obayx-2fvak-zersm-euci4-6pslt-lae to replica version [91732387a03c7c82bdaea6f78d7f8321cc8cb559](https://dashboard.internetcomputer.org/release/91732387a03c7c82bdaea6f78d7f8321cc8cb559)

• Proposal ID: 138310

  Update subnet 5kdm2-62fc6-fwnja-hutkz-ycsnm-4z33i-woh43-4cenu-ev7mi-gii6t-4ae to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138309

  Update API boundary nodes to GuestOS version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12) Motivation: update the API boundary nodes 4fssn-4vi43-2qufr-hlrfz-hfohd-jgrwc-7l7ok-uatwb-ukau7-lwmoz-tae.

• Proposal ID: 138308

  Update subnet mkbc3-fzim5-s5pye-pbnzo-uj5yv-raphe-ceecn-ejd6g-5poxm-dzuot-iae to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138307

  Update subnet vcpt7-niq42-6snup-7kcgy-cndz6-srq6n-h6vwi-oswri-a3guc-v5ssd-5qe to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138306

  Update subnet c4isl-65rwf-emhk5-5ta5m-ngl73-rgrl3-tcc56-2hkja-4erqd-iivmy-7ae to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138305

  Update subnet uzr34-akd3s-xrdag-3ql62-ocgoh-ld2ao-tamcv-54e7j-krwgb-2gm4z-oqe to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138304

  Update subnet 4zbus-z2bmt-ilreg-xakz4-6tyre-hsqj4-slb4g-zjwqo-snjcc-iqphi-3qe to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138303

  Update subnet ejbmu-grnam-gk6ol-6irwa-htwoj-7ihfl-goimw-hlnvh-abms4-47v2e-zqe to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138302

  Update subnet qxesv-zoxpm-vc64m-zxguk-5sj74-35vrb-tbgwg-pcird-5gr26-62oxl-cae to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138301

  Update subnet snjp4-xlbw4-mnbog-ddwy6-6ckfd-2w5a2-eipqo-7l436-pxqkh-l6fuv-vae to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138300

  Update subnet w4asl-4nmyj-qnr7c-6cqq4-tkwmt-o26di-iupkq-vx4kt-asbrx-jzuxh-4ae to replica version [91732387a03c7c82bdaea6f78d7f8321cc8cb559](https://dashboard.internetcomputer.org/release/91732387a03c7c82bdaea6f78d7f8321cc8cb559)

• Proposal ID: 138299

  Update subnet qdvhd-os4o2-zzrdw-xrcv4-gljou-eztdp-bj326-e6jgr-tkhuc-ql6v2-yqe to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138298

  Update subnet 2fq7c-slacv-26cgz-vzbx2-2jrcs-5edph-i5s2j-tck77-c3rlz-iobzx-mqe to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138297

  Update subnet pjljw-kztyl-46ud4-ofrj6-nzkhm-3n4nt-wi3jt-ypmav-ijqkt-gjf66-uae to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138296

  Update subnet 4utr6-xo2fz-v7fsb-t3wsg-k7sfl-cj2ba-ghdnd-kcrfo-xavdb-ebean-mqe to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138295

  Update subnet fuqsr-in2lc-zbcjj-ydmcw-pzq7h-4xm2z-pto4i-dcyee-5z4rz-x63ji-nae to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138294

  Update subnet shefu-t3kr5-t5q3w-mqmdq-jabyv-vyvtf-cyyey-3kmo4-toyln-emubw-4qe to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138293

  Update subnet xok3w-cnepj-fg6aa-cjitt-uoxod-4ddsy-nc7dq-zwudz-o6jar-rzstb-gqe to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138292

  Update subnet io67a-2jmkw-zup3h-snbwi-g6a5n-rm5dn-b6png-lvdpl-nqnto-yih6l-gqe to replica version [84a268e93a909a6827d76ad794411b161c839a12](https://dashboard.internetcomputer.org/release/84a268e93a909a6827d76ad794411b161c839a12)

• Proposal ID: 138291

  Update the unassigned nodes to the latest rolled-out version

• Proposal ID: 138290

  Update subnet tdb26-jop6k-aogll-7ltgs-eruif-6kk7m-qpktf-gdiqx-mxtrf-vb5e6-eqe to replica version [f7b2fdb7deb1758622f9c8e282d09ab8813aac62](https://dashboard.internetcomputer.org/release/f7b2fdb7deb1758622f9c8e282d09ab8813aac62)

• Proposal ID: 138289

  Register Rechenzentrum Ostschweiz AG datacenter as ar2 in Europe,CH,Appenzell Ausserrhoden. Additional documents: * Self Declaration Documents on IC Wiki: https://wiki.internetcomputer.org/wiki/Avalution_AG * Forum post: https://forum.dfinity.org/t/swiss-subnet-node-provider-onboarding-has-begun/55556/58 * Data center website: https://www.rechenzentrum-ostschweiz.ch/

• Proposal ID: 138288

  # Upgrade the Node-rewards Canister to Commit e3857ed __Proposer__: pietro.di.marco at dfinity.org __Source code__: [e3857ed56a35a75170e6d93ed98b84c169860f72][new-commit] [new-commit]: https://github.com/dfinity/ic/tree/e3857ed56a35a75170e6d93ed98b84c169860f72 ## Features & Fixes * Add get_node_providers_rewards endpoint, to be used by the Governance to compute performance-based rewards. * Store rewards (including intermediate results) in stable memory for client retrieval. * Add get_node_provider_rewards_calculation endpoint to compute ongoing rewards and fetch historical ones. * Add get_historical_reward_periods endpoint to fetch historical reward periods and the providers rewarded. * Fix rewards calculation algorithm to extrapolate with 0% failure rate node's performance for node providers with no assigned nodes on a given day. ## New Commits ``` $ git log --format="%C(auto) %h %s" 98b37bf4ffd2f46bc968018bb850a9753540877b..e3857ed56a35a75170e6d93ed98b84c169860f72 -- ./rs/node_rewards/canister ./rs/node_rewards ./rs/registry/node_provider_rewards 6fd65a9e53 feat(NRC): Add endpoint to fetch historical rewards (#6495) 4cdc4e66ec feat(NRC): Add rewards calculation endpoint (#6465) f398475d9c feat(NRC): Store rewards distribution in stable mem. (#6302) 7fb60c16d4 chore(nns): Release notes (#6295) e91e2af3ec fix(NRC): Remove limits on number of nodes (#6439) 91b252383a fix(NRC): Consider performance of assigned nodes below limit (#6382) 49d659c29d feat: Unify ic-cdk to v0.18.6 (#6264) eaee8f1c74 feat(NRC): Add get_node_providers_rewards endpoint (#6241) ``` ## Current Version __Current git hash__: 98b37bf4ffd2f46bc968018bb850a9753540877b __Current wasm hash__: 5cb2b88b043007b297a084cfe51820e83df836227b76ae140b897cb25f40e945 ## 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/e3857ed56a35a75170e6d93ed98b84c169860f72/rs/nervous_system/docs/proposal_verification.md ### WASM Verification See ["Building the code"][prereqs] for prerequisites. [prereqs]: https://github.com/dfinity/ic/tree/e3857ed56a35a75170e6d93ed98b84c169860f72/README.adoc#building-the-code ``` # 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 e3857ed56a35a75170e6d93ed98b84c169860f72 # 2. Build canisters. ./ci/container/build-ic.sh -c # 3. Fingerprint the result. sha256sum ./artifacts/canisters/node-rewards-canister.wasm.gz ``` This should match `wasm_module_hash` field of this proposal.

• Proposal ID: 138286

  ## 1. Adjust Node Provider ICP payments to automatically disburse 3% of gross earnings to neuron 4000934039483276792 for community development In order to help the Icp ecosystem, 3% from the gross node provider rewards will be directed to 6jvpj-sqaaa-aaaaj-azwnq-cai-wu6phoy.100000000010000000000000000000000000000000000000000000000000000, the address for the staking source of neuron 4000934039483276792. This will help relieve some of the pressure from the node provider redemptions of Icp tokens to pay for operating costs. By staking 3% of total rewards, nps will be further helping secure the network. upon the passing of this motion proposal, a follow up proposal will be made to adjust the network state to reflect this improvement.

• Proposal ID: 138285

  # Upgrade frontend NNS Dapp canister to commit `ae8fcd4f1b5be1bd48a7892a05e89212ef23e9c0` Wasm sha256 hash: `f2ed7ae8000e6b350e3e2d6060fedc5d58e0d19133f95eaec65683fa0f23973a` (`https://github.com/dfinity/nns-dapp/actions/runs/17288724971`) ## Change Log ### Added * Added support for additional chain-key tokens. #### Changed * Upgrade AgentJS to v3. ## Commit Log ``` + bash -xc "git log --format='%C(auto) %h %s' d5274ad04..ae8fcd4f1" ae8fcd4f1 Display more ck tokens (#7306) 4766c492d chore(deps): bump devalue from 5.1.1 to 5.3.2 (#7309) 7d8e23c2a style(cards): fix title layout and remove extra character (#7308) bbd94db39 bot: Update proposals candid bindings (#7302) 878406768 content(copy): improve application text clarity (#7297) 75c9bcda4 chore(table sorting): change naming of token sort chip (#7303) 89c455ddd fix(markdown): preserve heading styles when headings contain links (#7298) 16e7b9ed9 chore: Launchpad cleanup (#7292) f14ca6655 Update changelog after release (#7293) 459f4833f bot: Update SNS Aggregator Response (#7294) f82b8caa7 feat: migrate to AgentJS v3 (#7192) ``` ## Wasm Verification To build the wasm module yourself and verify its hash, run the following commands from the root of the [nns-dapp repo](https://github.com/dfinity/nns-dapp): ``` git fetch # to ensure you have the latest changes. git checkout "ae8fcd4f1b5be1bd48a7892a05e89212ef23e9c0" git merge-base --is-ancestor HEAD origin/main && echo "OK" || echo "Commit is not on main branch!" ./scripts/docker-build sha256sum nns-dapp.wasm.gz ``` You may also want to verify the canister arguments. In the proposal they are binary, which is not very readable. Docker provides both binary and text formats and you can verify that the text format corresponds to the binary `arg_hash` field in the proposal. ``` cat nns-dapp-arg-mainnet.did didc encode "$(cat nns-dapp-arg-mainnet.did)" | xxd -r -p | sha256sum ```