RSK PowPeg Hop 4.1.1.0

IMPORTANT: RSK consensus rules have changed in this version, which is incompatible with previous versions. If you've been running earlier versions of the RSK PowPeg client node in Mainnet, we encourage you to upgrade to this new version. The Mainnet network upgrade will happen at block number 4,976,300.

Please refer to the RSKj Hop v4.1.1 release for details about changes in this version.

RSK PowPeg Hop 4.0.1.0

IMPORTANT: RSK consensus rules have changed in this version, which is incompatible with previous versions. If you've been running earlier versions of the RSK PowPeg client node in Mainnet, we encourage you to upgrade to this new version. The Mainnet network upgrade will happen at block number 4,976,300.

Please refer to the RSKj Hop v4.0.1 release for details about changes in this version.

RSK PowPeg Hop Testnet 4.1.1.0 (Testnet-only version)

IMPORTANT: RSK Testnet consensus rules have changed in this version, and it is not compatible with previous versions (only for Testnet, this doesn't apply to Mainnet). If you've been running previous versions of the RSK client node in Testnet, we encourage you to update to this new version. The Testnet network upgrade will happen at block number 3,362,200. This is a non-mandatory upgrade for RSK Mainnet nodes.

Please refer to RSKj Hop Testnet v4.1.0 release for details about changes included in this version.

RSK PowPeg Hop Testnet 4.0.1.0 (Testnet-only version)

IMPORTANT: RSK Testnet consensus rules have changed in this version, and it is not compatible with previous versions (only for Testnet, this doesn't apply to Mainnet). If you've been running previous versions of the RSK client node in Testnet, we encourage you to update to this new version. The Testnet network upgrade will happen at block number 3,362,200. This is a non-mandatory upgrade for RSK Mainnet nodes.

Please refer to RSKj Hop Testnet v4.0.1 release for details about changes included in this version.

RSK PowPeg Hop 4.0.0.1

This release adds a new configuration setting that allows node operators to activate or deactivate transaction pegout signing, as shown below:

federator {
   pegout.enabled = [true/false]
}

The setting takes true as the default value

RSK PowPeg Hop 4.0.0.0

IMPORTANT: since consensus rules have changed, this version is not compatible with previous versions. If you've been running previous versions of the RSK client node, we encourage you to update to this new version. The Mainnet network upgrade will happen at block number 4,598,500. The Testnet network upgrade will happen at block number 3,103,000.

Please refer to RSKj HOP 4.0.0 release for details about changes included in this version.

RSK PowPeg Iris 3.3.0.0

Please refer to RSKj IRIS 3.3.0 release for details about changes included in this version.

RSK PowPeg Iris 3.2.0.0

IMPORTANT: RSK Testnet consensus rules have changed in this version, and it is not compatible with previous versions (only for Testnet, this doesn't apply to Mainnet). If you've been running previous versions of the RSK client node in Testnet, we encourage you to update to this new version. The Testnet network upgrade will happen at block number 2,581,800. This is a non-mandatory upgrade for RSK Mainnet nodes.

Please refer to RSKj IRIS 3.2.0 release for details about changes included in this version.

RSK PowPeg Iris 3.0.0.0

IMPORTANT: Since consensus rules have changed, this version is not compatible with previous versions. If you've been running previous versions of RSK client node, we encourage you to update to this new version. The Mainnet network upgrade will happen at block number 3,614,800. The Testnet network upgrade will happen at block number 2,060,500.

Please refer to RSKj IRIS 3.0.0 release for details about changes included in this version.

RSK PowPeg Papyrus 2.1.0.1

Please refer to RSKj IRIS 2.1.0 release for details about changes included in this version.