Skip to content
Back to Blog
Ecosystem Updates

RSK Hop 4.4.0 Is Here

Read Time: 1 mins
RSK Hop 4.4.0 Is Here

We are excited to unveil the latest version of the RSK Hop client, now available in the RSKj GitHub repository. This update brings performance enhancements, JSON RPC methods improvements, and Ethereum compatibility fixes, among other things.

Although this upgrade is not mandatory, we recommend that users upgrade their nodes to the latest version.

What changes are included in RSK Hop 4.4.0?

A non-comprehensive list of changes included in this version is:

  • Support named arguments in node’s CLI tools in #1893
  • Added JSON RPC timeouts & transaction gas cap limit validations in #1954
  • Improved eth_getLogs JSON RPC method performance in #1985
  • Enable cache.states.persist-snapshot setting by default in #1980
  • Included the type field in tx receipts and tx result responses for Ethereum libraries compatibility in #1984

You can find a complete list of the changes introduced in the corresponding GitHub milestone.

How do I upgrade to version 4.4.0?

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

RSKj Hop 4.4.0’s sha256 sum is 10e82f9e4fc80487f0e0799c4082275c2360e243d12fd791cb5108a05a71f7f8 rskj-core-4.4.0-HOP-all.jar. See the reproducible builds guide for further details.

How do I report problems with this version?

It’s essential for us to know any problem you may have while running Hop 4.4.0. Please reach out on RSK Open Slack or by creating issues in the 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 IOVlabs’ 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 Rootstock 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/rootstock_io

Telegram: https://t.me/rskofficialcommunity

Discord: https://discord.gg/fPerbqcWGE

Recommended articles

What Happened on Rootstock in February

What Happened on Rootstock in February

While markets reel, ₿uilders build. Despite turbulence in the wider crypto market, the Rootstock community kept focused on the long-term vision of making Bitcoin work for everyone. Building on a strong start to the year, February was another big month with institutional adoption accelerating, infrastructure hardening, and the ecosystem showing up on the global stage. […]

Ecosystem Updates
Reed 8.1.0: RSKj Client Release and Testnet-only Network Upgrade

Reed 8.1.0: RSKj Client Release and Testnet-only Network Upgrade

We are pleased to announce the release of RSKj Reed 8.1.0, the latest version of the RSKj client. As approved by the Rootstock community as part of the Reed upgrade, this version introduces a set of consensus changes that will activate only on Testnet, along with RSKj node optimizations for improved performance, stability, and better […]

Developer Resources
Token Bridge Sunset: How to Move Your Assets and Bridge to Rootstock via Stargate

Token Bridge Sunset: How to Move Your Assets and Bridge to Rootstock via Stargate

Rootstock is deprecating the Token Bridge (Ethereum ↔ Rootstock). Bridging via the Token Bridge will no longer be supported after the end of March 2026. For bridging into Rootstock going forward, we recommend using Stargate. What’s changing Token Bridge bridging between Ethereum and Rootstock will no longer be supported after the end of March 2026. […]

Ecosystem Updates