RSK Hop Testnet 4.0.1 and 4.1.1 Are Here (Testnet-only versions)
Summary: The RSK Testnet network will undergo a patch network upgrade on block #3,362,200. This is a mandatory upgrade exclusively for Testnet; users must update their nodes to the latest version.
As described in the RSK peg-out service outage incident report published a few weeks ago, the RSK Core Development team is currently working on a definite solution to the peg-out service issue. As part of the defined action plan, and in preparation for the Mainnet release, we are today making a Testnet-only patch release available to the general public. This new RSK release has been published in our GitHub repository and contains consensus changes that will activate on Testnet on block #3,362,200.
We are making two new releases available:
- RSK Hop Testnet 4.0.1: recommended release for users running RSK Hop 4.0.0.
- RSK Hop Testnet 4.1.1: recommended release for users running RSK Hop 4.1.0.
This is a patch network upgrade exclusively for RSK Testnet. All nodes in the network need to run a compatible client version supporting these new consensus rules to work correctly. Consequently, if you adhere to these changes, you must upgrade to the desired new client version before the network upgrade is activated on Testnet. Otherwise, the non-updated nodes will remain on an incompatible chain.
What changes are included in Hop Testnet 4.0.1 and 4.1.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.
When will the Testnet network upgrade happen?
RSK Hop Testnet 4.0.1 and 4.1.1 will activate at block #3,362,200. According to the current conditions of the network, activation is likely to occur on Tuesday, November 22nd, 2022. Depending on the RSK Testnet network’s average block time progresses, this date can change.
Is there anything I need to consider when upgrading to Hop Testnet 4.0.1 or 4.1.1?
There is no other special consideration besides updating your node before the network upgrade activation happens at the defined block number.
RSKj Hop Testnet 4.0.1’s sha256 sum is 1dfb2936f7ae0d8bad51607c1df18a9ad370a28ba99cae4e27cb4c13a6116719 rskj-core-4.0.1-HOP-TESTNET-all.jar.
RSKj Hop Testnet 4.1.1’s sha256 sum is 6999deb8b6266cd64e2f408bf3b748904348083f6a678b92cf7b43223f643d6c rskj-core-4.1.1-HOP-TESTNET-all.jar.
See the Reproducible Build guide for further details.
When will the peg-out service be resumed on RSK Mainnet?
Having the patch released and activated on Testnet will let us confirm that the proposed fix works as expected in an environment that is very similar to Mainnet. We expect this to be the last step before moving forward with a definite solution to the issue on the RSK Mainnet network. We will keep the RSK community informed about the next steps once this is finished on Testnet.
How do I report problems with this version?
It’s essential for us to know any problem you may have while running Hop Testnet 4.0.1 or 4.1.1. Please reach out on RSK Open Slack or directly through creating issues in the RSK GitHub repository.
How do I report security vulnerabilities?
If you find a security issue, please get in touch with us at firstname.lastname@example.org, or report it through our bug bounty program. We reward security experts, software developers, and hackers who dedicate time and effort to improving and protecting the RSK platform.
Do you have further questions?
Please get in touch with us through our RSK Open Slack for technical questions and support.
You can also reach out with any feedback you would like to share with us through our social media channels and forums: