Release Notes for new replica version 50ead

Announcements
1

Dear IC Community,

we are happy to announce a new replica version that will get proposed to be elected within the next 48 hours.
The release notes are as follows:

* Consensus: Allow 30 seconds drift when http_handler checks max ingress expiry time
* Consensus: Create CUP shares at all summary heights
* Consensus: Load iDKG transcript before creating tECDSA signature share
* Consensus: Only fetch CUP shares when they are relevant
* Consensus: Purge tECDSA signature shares
* Consensus: Signed interactive DKG dealings
* Consensus: Remove `ingress_bytes_per_block_soft_cap` from Registry
* Execution: Account the message overhead towards the instruction limit
* Execution: Add page content validation for mmap-based pages
* Execution: Added support for custom canister metadata sections
* Execution: Fix instruction limit for canister upgrades
* Execution: Improve pipelining of queries
* Execution: Separate thread-pools for cleanup, queries, and updates
* Execution: Set certified data in sandbox
* Message Routing: Fix system subnet stream message limits
* Node: Account for memfd RSS footprint
* Node: Make root fs readonly
* Orchestrator: Fetch subnet CUP from a single peer
* Orchestrator: Increase MAX_NUM_SSH_KEYS from 100 to 130
* Various bugfixes and test updates
8 Likes
2

There is something special with this new release that we never did before and that we want to point out.
The canister sandboxing that is mentioned in the release notes is actually not enabled yet.
To test it carefully we will propose another replica version to be elected that has this new feature enabled. This version will only be rolled out to the k44fs app subnet. If you run a canister in that subnet and are observing any anomalies please reach out to us. You can check in which subnet your deployment is running by pasting your canister id into the search bar of the public IC dashboard.

If you want to learn more about the new canister sandboxing feature we would recommend you a community conversation about that topic next week Tuesday 19:00 UTC.

4 Likes
3

The proposal to elect the first version with the disabled sandboxing feature was placed.

2 Likes
4

And the rollout to the first subnet has started :crossed_fingers:

2 Likes
5

And here we go with the enabled sandboxing version.

1 Like
6

This release was successfully rolled out today by updating the NNS subnet.
The next RC is ready.