Voting is open for a new IC release - ef8ca68

Governance
1

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

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

  • [b9f758ac9] Consensus: (De)Serialize CanisterHttpPayload on a per message basis
  • [6cc4f73da] Consensus: chore: remove some code duplication in block_maker.rs
  • [20ec47dc3] Consensus: chore(ic-recovery): two small fixes
  • [e38c7a762] Consensus: feat(consensus): Improve serialization consistency in ArtifactPool
  • [969305ab2] Crypto: chore: Upgrade ic_bls12_381 crate to 0.8.0
  • [456ffd06b] Crypto: chore: use TimeSource for generating TLS certificates
  • [cba6fa11b] Crypto: feat: Add epoch metrics for NI-DKG loaded and retained transcripts
  • [70133ae94] Message Routing: Extend the SubnetRecordBuilder to include membership (list of node ids) and the maximum number of canisters parameters.
  • [0814a0cf4] Message Routing: fix: Safer ic_types::Time operations
  • [fe03dd1fb] Networking: chore: Add JoinMap async util
  • [e8808c9e2] Networking: chore: Use HTTPS for fetching NNS delegation
  • [91dec61ae] Networking: chore: use the same tokio runtime for both xnet server and client
  • [d26d22375] Networking: feat: State sync manager interface
  • [7ef0ead15] Networking: fix: remove the unused replica_config proto
  • [519ee2b9a] Node: Add deterministic network utils crate
  • [adff60c44] Runtime: Enable Wasm-native stable memory
  • [7253e97ab] Runtime: Fix memory grow for canisters with memory allocation
  • 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 ef8ca68771baa20a14af650ab89c9b31b1dc9a5e
if ./gitlab-ci/container/build-ic.sh -i ; then
    curl -LO https://download.dfinity.systems/ic/ef8ca68771baa20a14af650ab89c9b31b1dc9a5e/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.

1 Like
2

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 123248 in the CodeGov portal on DSCVR. The CodeGov neuron 2649066124191664356 has voted to adopt proposal 123248.

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.