IMPORTANT: this release is still marked as pre-release and is subject to change. It is not recommended to use in a production environment until the pre-release tag is removed.
Summary
This release introduces remediation to the peg-out service issue in RSK Mainnet, as described here. However, the peg-out service will resume operations when the PowPeg address is updated and the new redeem script activated (date not defined yet, will be announced soon).
Since consensus rules have changed, this version is incompatible with earlier versions. Consequently, if you adhere to these changes, you must upgrade to the new client version before the network upgrade is activated. Otherwise, the non-updated nodes will remain on an incompatible chain. The Mainnet network upgrade will happen at block number 4,976,300.
We encourage you to upgrade to this new version if you are running version 4.0.0 of the RSK client node. If you are running version 4.1.0 of the RSK client node in Mainnet, we recommend upgrading to this version instead.
What's New in RSKj 4.0.1
The consensus changes included in this version are:
- Align RSK P2SH redeem script with Bitcoin Core standard transactions checks (RSKIP-353)
- Adjust the number of block confirmations for a PowPeg migration period (RSKIP-357)
For a detailed description of each consensus change introduced in this network upgrade, please refer to RSKIP 358 Network Upgrade (patch): Hop 4.0.1. You can also find a complete list of the changes introduced in the corresponding GitHub milestone.
Full Changelog: HOP-TESTNET-4.0.1...HOP-4.0.1
Reproducible Build
SHA256 (see Reproducible Build guide for further details): 0ed5aa42ba590be6d4947ac48362af57e46f4f228d554a1c26f79e84a0784dc1 rskj-core-4.0.1-HOP-all.jar