Skip to content
This repository has been archived by the owner on Feb 19, 2024. It is now read-only.

1.3.0
Compare
Choose a tag to compare
@dhedey dhedey released this 27 Jun 14:05
· 2 commits to release/1.3 since this release
1.3.0
d66a496
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

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.

Assets 3
Loading