Scroll down
Close -

Iris v3.0.0 is Here: What You Need To Know About RSK Upcoming Network Upgrade

Summary: The RSK network will be undergoing a planned network upgrade soon. The exact activation height is yet to be approved by the RSK community. The main purpose of this next network upgrade is to address several issues identified by the RSK community that will improve security, foster decentralization, simplify user experience and continue supporting the current strong growth of the ecosystem. This blog post shares all the relevant information users need to know about the upcoming upgrade.

What is a network upgrade?

A network upgrade is a set of changes to the protocol consensus rules, which are activated at a defined block number. All nodes in the network need to run a compatible client version implementing these new consensus rules to work properly. As a consequence, if you adhere to these changes, you will need to upgrade to the new client version before the network upgrade is activated. Otherwise, the non-updated nodes will remain on an incompatible chain.

When will the network upgrade happen?

The definition for the Iris’ activation block numbers is still pending the RSK community approval, to happen after the upcoming RSK Community Call (to be announced). The tentative block numbers are block number 3,589,500 for Mainnet and block number 2,027,200 for Testnet. According to the current conditions of the network, if those block numbers are confirmed, Mainnet activation is expected to occur on Tuesday, August 10th, 2021, while Testnet activation is expected to occur on Friday, July 23rd, 2021.

How do I upgrade to version 3.0.0?

When the final release of RSKj Iris v3.0.0 is available, users will need to download and update their RSKj node to this new version before the upgrade is activated. An RSKj Iris release candidate version is already available in our Github repository. Since changes to block activation numbers may still happen, we encourage users to use this release only for testing purposes.

What changes are included in Iris v3.0.0?

These are the most relevant consensus changes included in this version:

  • Add BLAKE2 compression function F precompile (RSKIP153)
  • Enable 2WP peg-in transactions to any RSK address (RSKIP170).
  • Flyover protocol consensus changes (RSKIP176).
  • BTC-RSK timestamp linking protection (RSKIP179).
  • Enable refunds for 2WP peg-out transactions with invalid amounts (RSKIP185)
  • Time-locked emergency multisignature (RSKIP201).
  • Reduced 2WP peg-in and peg-out minimum amounts (RSKIP219).
  • Open Bitcoin blockchain oracle (RSKIP220).

These are the most relevant non-consensus improvements included in this version:

  • Improvements and compatibility fixes at the JSON-RPC interface (#1481, #1482, #1483, #1451, #1352, #1299, #1339, #1284)
  • New “rewind” feature added to CLI tool (#1443)
  • Block propagation enhancements (#1326)
  • Node performance improvements (#1327)
  • Use native library for public key recovery in signatures (#1258)
  • Add Java11 support (#1252)

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

Is there anything I need to consider when upgrading to Iris 3.0.0?

This version does not require any special consideration apart from updating your node before the network upgrade activation happens at the defined 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 Iris 3.0.0. Please reach out on RSK Open Slack or directly through creating issues in RSK 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 contact 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:





If you are new to RSK, you may want to check RSK Developers Portal to find out how to start building on the RSK platform.