Scroll down
Close -

Papyrus v2.0 is Here: What You Need To Know About RSK Upcoming Network Upgrade

Summary: The RSK network will be undergoing a planned network upgrade at block number 2,392,700. This is expected to occur on Friday, May 29th, 2020. This blogpost shares all the relevant information users need to know to successfully upgrade their RSK nodes to this new version.

May 6th Update – IMPORTANT UPDATE: some users reported that after upgrading to v2.0.0, they have experienced peer disconnections in their nodes. We’ve released a patch version to better handle timeout and peer disconnection scenarios. Download and update your RSKj node to Papyrus v2.0.1 before the upgrade is activated. Please note that users running rskj Wasabi v1.3.0 or previous don’t need to install rskj Papyrus v2.0.0 before installing this patch. Users running v2.0.0 are highly encouraged to update to this new version. This release is already available in our Github repository. This blogpost has been updated to reflect these changes.

What is a network upgrade?

A network upgrade is a change or group of changes to the protocol consensus rules, which are activated at a defined block number. As a consequence, if you adhere to these changes, please upgrade to the new client version before the network upgrade is activated. Otherwise, the non-updated node will remain on an incompatible chain.

When will the network upgrade happen?

Network upgrade activation for RSK Mainnet will happen at block number 2,392,700. According to the current conditions of the network, this is expected to occur on Friday, May 29th, 2020.

In the case of RSK Testnet, the upgrade will happen at block number 863,000, expected to occur on Tuesday, May 19th, 2020.

How do I upgrade to version 2.0?

Download and update your RSKj node to Papyrus v2.0.1 before the upgrade is activated. This release is already available in our Github repository and can be done from any previous version.

What changes are included in Papyrus v2.0?

This is a summary of the most relevant changes included in this version:

  • Garbage Collector v0.2, includes improvements to the previously released garbage collection feature (beta version*).
  • Import sync v0.1 feature will let users sync their nodes in a fraction of the time currently required (beta version*).
  • Added support for segwit (P2SH-P2WPKH) peg-in transactions in RSK 2-way peg (after network upgrade activation).
  • Additions to the 2WP process (locking cap and improvements to the return of funds logic) in preparation for the whitelisting mechanism removal (after network upgrade activation).
  • Added support for logs subscription in eth_subscribe JSON RPC method.
  • Added ECADD, ECMUL and PairingCheck precompiled contracts (after network upgrade activation).
  • Added CHAINID, SELFBALANCE and EXTCODEHASH opcodes (after network upgrade activation).

(*) These features are still in beta, meaning they are not yet reliable to be used in a production environment and are disabled by default. Please refer to RSK Developer Portal for further information.

For a detailed description of the consensus changes introduced in this network upgrade, please refer to RSKIP 141 Network Upgrade: Papyrus. You can also find a complete list of the changes introduced in the corresponding Github milestone.

RSKj Papyrus 2.0.1’s sha256 sum is 43149abce0a737341a0b063f2016a1e73dae19b8af8f2e54657326ac8eedc8a0 rskj-core-2.0.1-PAPYRUS-all.jar. See Reproducible Build guide for further details.

Is there anything I need to consider when upgrading to Papyrus 2.0?

This version does not require any special consideration apart from updating your node before the network activation happens at the specified block number.

How do I report problems with this version?

It’s really important for us to know any problem you may have while running Papyrus 2.0.1. Please reach out on our Gitter community or directly through creating issues in our Github repository.

How do I report security vulnerabilities?

If you find a security issue, please contact us at, or report it through our bug bounty program. We reward security experts, software developers and hackers who dedicate time and effort to improve and protect the RSK platform.

Do you have further questions?

Please reach out with any feedback you would like to share with us through our social media channels and forums:






If you are new to RSK, you may want to check our developer portal to find out how to start working on the RSK platform.