Voting is open for a new IC release - 0062aec2

Hello there!

we are happy to announce that voting is now open for a new IC release .
The NNS proposal is here: IC NNS Proposal 123711 .

Here is a summary of the changes since the last release:

  • [287a3ad9a] Consensus: chore(ic-recovery): get batch_time from the source subnet cup
  • [ec47fa42e] Consensus: chore: Only depend on ic-backtrace on linux for Cargo
  • [e48b263e1] Crypto: feat: Add IBE implementation into vetkd packages crate
  • [da3667ca3] Execution: chore: make payload exceeded error message more readable
  • [9068dd971] Execution: fix: Charge for message memory consumed by canisters
  • [11584a629] Message Routing: feat: 64kB write buckets
  • [362d410c1] Networking: feat(firewall): Add UDP protocol to whitelisting of nodes.
  • [32534b23e] Networking: feat: Improve quic transport metrics
  • [a17e1a392] Networking: fix(firewall): Add all nodes in registries since last CUP to node whitelist
  • [5316facfc] Networking: fix: Lower quic transport connection timeout
  • [21a6d1b32] Networking: fix: Quic transport dialer reconnect and no topology membership
  • [942cc5a17] Networking: remove unused crates and update the actix-web version
  • [7437eac22] Node: Fix bug preventing config partition from populating in SetupOS
  • [2eff56a9e] Node: Update admin file path in config partition
  • [70f194231] Node: Update guestos to include guest kernel for SEV-SNP
  • [1fb8e784a] Node: Update terminal logs to increase NP clarity
  • [d6256d968] Runtime: Add Wasm function complexity metric
  • [338505e79] Runtime: Add a field for resource reservation to replicated state
  • [0d13c039a] Runtime: Add a subnet memory threshold config parameter
  • [f0c1672b6] Runtime: Upgrade wasmtime to version 10.0.1
  • Various tech-debt management: code refactoring, docs, bug fixes, test updates

IC-OS Verification

To build and verify the IC-OS disk image, run:

# From https://github.com/dfinity/ic#building-the-code
# This process requires an x86-64 based machine, Ubuntu 20.04 or a newer version of the OS, Git, and Podman.
git clone https://github.com/dfinity/ic
cd ic
git fetch origin
git checkout 0062aec2efc16d6e4cadb2cd1052aaabbc9f6e48
if ./gitlab-ci/container/build-ic.sh -i ; then
    curl -LO https://download.dfinity.systems/ic/0062aec2efc16d6e4cadb2cd1052aaabbc9f6e48/guest-os/update-img/update-img.tar.gz
    shasum -a 256 artifacts/icos/guestos/update-img.tar.gz update-img.tar.gz
else
    echo "IC-OS build failed. Verification unsuccessful." >&2
fi

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.

Reviewers for the CodeGov project have completed our review of this replica update and our findings from the reviews can be viewed in this post for proposal 123711 in the CodeGov portal on DSCVR. The CodeGov neuron 2649066124191664356 has voted to ADOPT proposal 123711.

At the time of this comment on the forum, there are still 2 days left in the voting period. We encourage NNS voters to review the replica update proposal and vote manually. Of course, you always have the choice to follow another person or another organization who is voting independently. At this time, I am aware of CodeGov.org (neuron ID 2649066124191664356) and Taggr Network (neuron ID 16737374299031693047) who are performing this work, both of which are registered known neurons. You can learn more about the CodeGov project at CodeGov.org and you can learn more about Taggr Network in the NNS-GOV realm on taggr.top

NOTE: The CodeGov project would like to find additional reviewers to help with this work. Since there is a 0.5 - 2 hour time commitment on the weekend for each proposal and our reviews require technical skills, we offer a bounty for every review that you perform that is competitive with typical developer contract work. You are not required to review every proposal, but we encourage as much participation as your time allows. Anyone who has the technical skill to perform the IC-OS verification and who is willing to perform a sanity check on the Release Notes is welcome to be a reviewer. If you are interested, then please Apply at codegov.org. The current bounty for this work can always be found in this post in the CodeGov portal.

Also, let me offer a special welcome to @ZackDS to the CodeGov project as a new reviewer. He started with an excellent review this week. Thank you for your help!

2 Likes