Skip to content
Back to Blog
Ecosystem Updates

Iris Release v3.3.0 Is Here

Read Time: 2 mins
Iris Release v3.3.0 Is Here

We’re pleased to announce that a new RSK Iris release has been published in our GitHub repo. This release contains enhancements to the node’s JSON-RPC interface, as well as Ethereum compatibility fixes and robustness enhancements. While this is a non-mandatory upgrade, we encourage users to upgrade their nodes to the new version.

How do I upgrade to version 3.3.0?

There are no special considerations for upgrading to this version. Users need to download and update their RSKj node and no other task is required. 

RSKj Iris 3.3.0’s sha256 sum is cce6c949251d1ee6d9ab8bf1d29e026778a846f048a854ca5ef114000b05f079 rskj-core-3.3.0-IRIS-all.jar. See Reproducible Build guide for further details.

What changes are included in Iris v3.3.0?

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

  • Fixed web3_sha3 method for non-hex encoded strings in #1637
  • JSON-RPC compatibility fixes in #1659
  • eth_getLogs method performance improvements in #1650
  • Mitigated db inconsistency issue after improper node shutdown in #1660
  • Enabled fast block propagation mode by default in #1677
  • Added tracing options to debug_traceTransaction method in #1644

You can find a complete list of the changes introduced in Iris 3.3.0 milestone.

How do I report problems with this version?

It’s really important for the whole RSK community that users report any problem they may have while running RSKj Iris 3.3.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 security@rsk.co, 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:

Twitter: https://twitter.com/RSKsmart

Telegram: https://t.me/RSKsmart

Reddit: https://www.reddit.com/r/rootstock/

BitcoinTalk: https://bitcointalk.org/index.php?topic=3189777.0

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.

Recommended articles

Can AI Build a Second Rootstock Client? Lessons from a Rust Experiment

Can AI Build a Second Rootstock Client? Lessons from a Rust Experiment

Disclaimer: rustock is a personal experiment exploring how far today’s AI coding tools can go. It is not an official Rootstock client, has not been security reviewed, and should never be used in production.   One of the biggest long-term challenges for any blockchain is client diversity. Independent implementations make networks more resilient by reducing […]

Research & Innovation
Vetiver 9.0.3: Patch Release

Vetiver 9.0.3: Patch Release

This patch release fixes the issue reported in #3543 affecting the JSON-RPC API methods trace_transaction and trace_block. It also includes code readability improvements, minor bug fixes, and enhanced logging. Although this is not a mandatory release, nodes that rely on these tracing methods should be updated to this version to avoid potential issues. The latest […]

Ecosystem Updates
Simplifying DAO Development with the Rootstock Collective SDK

Simplifying DAO Development with the Rootstock Collective SDK

The Rootstock Collective SDK is the easiest way for developers to integrate with the Rootstock Collective DAO. Designed with modern dApp development in mind, it abstracts the complexity of interacting with multiple smart contracts into a clean, modular, and type-safe TypeScript interface. Built on top of viem, the SDK delivers a familiar, high-performance experience, especially […]

Developer Resources