Node Releases & Hard Forks

Following the recent release of node software v1.1.1, the team have advised on a number of further releases which are planned over the next new months to implement coordinated forking. This will initiate a fork to an updated protocol, only when a certain threshold of validators (or stake weight) have upgraded. Validators who have not updated by a prescribed time, will be removed from the validator set until they do so.

Furthermore, an update for Validator Liveness Assurance is planned in June which will temporarily remove validators from the set if they don’t meet the required liveness standards. See details below (source: Radix Discord)

:arrow_right: Node version 1.1.1 released 22nd April 2022. It’s a recommended reliability upgrade, and should be an easy upgrade from 1.1.0 - more details here:

:arrow_right: 1.2.0 - Support for co-ordinated forking [Releases early May]

This release will enable nodes to recognise fork votes. We’re hoping to have documentation, a new CLI version, and a release candidate available for testing some time next week. As part of preparing for this release, we will run through the process of a hard fork on Stokenet, and we’ll ask for node runners’ assistance with testing this. This will hopefully ready for stokenet testing in the middle of next week.

:arrow_right: 1.3.0 - The first candidate fork [Likely releases around mid-May, with fork hopefully enacting around the end of May]

This will capture updates to the fee table. Node runners will need to install the new version of the software, and validators will be taken through the process to vote for the fork. There will be a grace period between the version being released and the fork being able to enact. When the fork is enacted, nodes running old versions of the software will be unable to continue syncing past the fork point.

:arrow_right: 1.4.0 - Validator Liveness Assurance [Potentially releases early June, with fork enacting soon after a few weeks later]

Our second candidate fork. This update will “jail” validators who don’t meet sufficient liveness guarantees, ensuring validators who crash or fail to meet reasonable liveness standards will be temporarily removed from the validator set, ensuring the network stays running smoothly. More details will follow in due course.


For the systemd runners out there, don’t forget to add the --enable-preview to the JAVA_OPTS or your node won’t start at all.