1.5.0-stokenet

This is a STOKENET only release for the 2nd migration test. You should use 1.5.0 (without any suffix) on your mainnet nodes.

This release is purposefully a pre-release, to save confusing node runners updating for the mainnet babylon switchover. This means this release won't be picked up by your radixnode CLI and will have to be configured manually, say by updating your radixnode configuration files.

Overview

This release replaces the existing Stokenet shutdown fork with a new one, so that it can be used for the 2nd public migration test.

Please use the following seed node configuration with this build:

radix://tn1qvu75s52hz8k2dq6pesed07mwrur3frq0mvvdu9d700txpx80jzljde4hzg@54.75.151.219,radix://tn1qv9f8ys7ade4khjyr2s6zlhuxjqvhzz39kvjskupaj9lvhl3lwxauc67nn8@13.232.171.17,radix://tn1qv89yg0la2jt429vqp8sxtpg95hj637gards67gpgqy2vuvwe4s5s7c07sm@65.1.193.226,radix://tn1qvtd9ffdhxyg7meqggr2ezsdfgjre5aqs6jwk5amdhjg86xhurgn5kfxgl5@13.54.68.41,radix://tn1qwz237kqdpct5l3yjhmna66uxja2ymrf3x6hh528ng3gtvnwndtn5d8q7h2@35.169.1.21,radix://tn1qwfh2nn0zx8cut5fqfz6n7pau2f7vdyl89mypldnn4fwlhaeg2tvuakynag@52.209.65.180,radix://tn1q2hs6rwjg8jscllzmp4dage6tjuequwhdvrnvx86vpw5g68zyxl9j7x87n2@35.154.73.229,radix://tn1qtx35eknnnefue4wdra9j3ugld0j5hlpfmnr36npjydranz3d4ys6wpnm3a@18.203.104.173,radix://tn1q050yda7ek7lvchnwh9kj9955mz9sz05mjw5thcz90z80zvvjcu3ktejs83@54.79.51.223

Full details on how to configure this node for the stokenet migration test - including a test ledger to copy - are available on our babylon docs site here.

1.5.0

Overview

This release version includes a coordinated protocol update that shuts down Olympia mainnet (which is estimated to be enacted on or about 2023-09-27, at which time mainnet will migrate from Olympia to Babylon).

The protocol update requires 79% of an active validator set to signal their readiness and can be enacted between epochs 32718 and 32723. Refer to https://docs.radixdlt.com/main/node-and-gateway/coordinated-protocol-updates.html for more information on coordinated protocol updates.

This release also includes changes to the /olympia-end-state Core API endpoint: it is no longer a part of the Core API. Instead, it runs on its own http server, which allows to expose it on an external address, while keeping the Core API internal.
It can be configured using the following parameters: api.end-state.bind.address/api.end-state.port (default 0.0.0.0:3400).
Core API now defaults to 127.0.0.1:3333 (which can be changed using api.bind.address/api.port).

If you haven't already, you will need to run a Babylon node after the switchover. If you wish to have your nodes automatically update, please see the introduction to the Olympia Babylon migration.

1.5.0-rc.1

Testing pre-release

1.4.0

Overview

This release version includes a coordinated protocol update that shuts down Olympia Stokenet (which is scheduled to be enacted on Monday Jul 10, at which time Stokenet will migrate from Olympia to Babylon) and minor improvements around shutdown and related core API endpoints.

Node runners who wish to participate in Stokenet Olympia to Babylon migration must update their nodes to this version by Jul 10, 9 am UTC time. Refer to this doc page for information about the migration in general, and this page for Stokenet-specific docs.

This release doesn't affect Olympia mainnet, nor does it contain any significant changes/improvements. Mainnet node runners may update to this version at their wish.

1.3.3

Overview

This release version brings a fix to mitigate issues seen by some full nodes struggling to sync past state version 282790161 (which occurred at 2023-05-04 16:55:41.9 UTC), and protects from similar issues in future.

We recommend all node runners to run this build.

Recent ledger backup

You shouldn't need to use this backup if you install release version 1.3.3, but we are including this for completeness

If anyone has wiped their full node as part of working around this issue, a backup of the ledger (with transaction stream enabled) from this weekend is available here to allow you to get back up to speed sooner.

1.3.2

Overview

This release version brings maintenance updates with no backward compatibility breaks in terms of functionality or API surface, but deployment:

• Updates the base Ubuntu images and adds support for ARM images.
• Implements Olympia engine shutdown

Details for node runners

Node runners need to update their hosts to use Docker version 20.10.10 or newer and make sure node CLI is updated. See this.

1.3.1

IMPORTANT

The first Radix Network Protocol Update enacted at the start of epoch 14493, on Tue 12th July at 22:05:51 UTC. This node release hard codes that epoch as a fixed epoch protocol update.

Any node that did not upgrade in time to 1.3.0 should upgrade to 1.3.1, and can continue syncing.

If your node is on 1.3.0 and successfully updated to the new protocol version at epoch 14493, you may upgrade to 1.3.1 if you wish, but there is no need to, as there are no functional changes in this version.

Details for node runners

A new version (1.3.1) of the node CLI accompanies this release.

This release should be a straightforward update from 1.3.0, 1.2.x, 1.1.1.

If upgrading from 1.1.0 or below, please check out the 1.1.1 release notes. Note in particular the following:

• If running the Jar directly or directly/indirectly providing custom JAVA_OPTS, the flag --enable-preview needs to be added at the start of the JVM start parameters for the node to start.

If upgrading from 1.0.X, please also check out the 1.1.0 release notes. Note in particular the following:

• You will need to upgrade your Java version to 17.

Note: If running a bare metal jar on Windows, avoid Open JDK 17.0.3 due to this bug. 17.0.4 should be fine.

1.3.0

IMPORTANT

When the fork in this release enacts, any node running a version older than 1.3.x will stop.

Overview

This release includes a Candidate fork for the first Radix Protocol Fork, as per the recent blog post and published policy.

This candidate fork, when enacted, will adjust the fee table, and emissions-per-proposal, in line with the changes to network speed and XRD price since the original values were calculated. Roughly, XRD fees will reduce by 42%, and emissions per proposal will drop slightly by 22% to be in line with the 300M/year target. For full details on the calculations, see the PR here: #702

Depending on when validators signal readiness, the fork may occur sometime between Monday 2022-07-11 and Thursday 2022-07-28, with 7 days warning.

Details for validators

Any validators updating to this version will need to signal readiness, using the Node CLI v1.2.2+ or a direct call to the node's Core API. Please read the docs on co-ordinated forking here for more information. Signaling readiness requires the key sign endpoint of your Core API turned on. You should make doubly sure your Core API is not publicly exposed before doing this. See the coordinated forking docs for more information.

See details for node runners below for information on the upgrade path to 1.3.0.

Details for node runners

This release is accompanied by the 1.3.0 release of the Node CLI.

This release should be a straightforward update from 1.2.x or 1.1.1.

If upgrading from 1.1.0 or below, please check out the 1.1.1 release notes. Note in particular the following:

• If running the Jar directly or directly/indirectly providing custom JAVA_OPTS, the flag --enable-preview needs to be added at the start of the JVM start parameters for the node to start.

If upgrading from 1.0.X, please also check out the 1.1.0 release notes. Note in particular the following:

• You will need to upgrade your Java version to 17.

Note: If running a bare metal jar on Windows, avoid Open JDK 17.0.3 due to this bug. 17.0.4 should be fine.

1.2.2

Overview

This is the Node 1.2.2 release, its primary feature is to add support for co-ordinated forks.

This release does not contain any candidate forks, but be advised there will be a candidate fork released in the next few weeks, and we expect (after a week or so of enforced grace period), there will be a hard fork of the Olympia network soon after. Any nodes not running the version with the candidate fork will stop being able to ingest the ledger after the fork point.

For more information, see our docs page on co-ordinated forks.

This release also includes other key changes regarding network reliability and closing a memory leak when syncing as a validator.

Notes for node runners

• There is a new CLI version which accompanies this node version, which includes the ability for validators to mark readiness on ledger for candidate forks.
• There are some new metrics and data in existing endpoints related to co-ordinated forking, as described in our docs page on co-ordinated forks

Otherwise, this should be a straightforward upgrade from 1.1.1. If upgrading from before 1.1.1, please check the release notes for all release versions that you have missed.

Change Summary

More detailed changelog is included on the release candidates:

• 1.2.0-rc.1
• 1.2.1-rc.1
• 1.2.1-rc.2

1.2.1

This is a release candidate. We’d advise against using this version on mainnet until the official release.

This release has been superseded by 1.2.2