Skip to content
Back to Blog
Ecosystem Updates

RSK Hop 4.1.0 Is Here

Read Time: 2 mins
RSK Hop 4.1.0 Is Here

We’re pleased to announce that a new RSK Hop release has been published in the RSKj GitHub repository. This release brings new JSON-RPC tracing methods, support for the latest versions of Hardhat development environment, the introduction of a peer reputation system, and support for RocksDb storage library, among other things. While this is a non-mandatory upgrade, we encourage users to upgrade their nodes to the new version.

How do I upgrade to version 4.1.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.1.0’s sha256 sum is d5ec4c766b184d13dde8c4cdef6f30481731b72c562c087bfd0c223d5709a2e6 rskj-core-4.1.0-HOP-all.jar. See the reproducible builds guide for further details.

What changes are included in Hop 4.1.0?

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

  • Fixed corner case bug in eth_estimateGas JSON-RPC method in #1803.
  • Accept websocket connections without requiring the “websocket” suffix in the URL path in #1753.
  • Improved the eth_gasPrice method by fetching historical gas prices from DB at node startup in #1724.
  • Added Content-Length and Connection headers to JSON-RPC responses, solving issues Hardhat users had when interacting with RSKj, in #1836.

You can find a complete list of the changes introduced in the Hop 4.1.0 milestone.

NOTE: features marked as [experimental] are disabled by default. They require further validation and should only be used with caution. They can be changed or removed in future releases of the node. If you don’t know what these features are or their possible impact, you likely should not enable them.

How do I report problems with this version?

It’s essential for the whole RSK community that users report any problem they may have while running RSKj Hop 4.1.0. 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 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/rskofficialcommunity

Discord: https://discord.gg/fPerbqcWGE

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

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

Recommended articles

Parallel Transaction Execution: Why Blockchain Needs to Learn to Multitask

Parallel Transaction Execution: Why Blockchain Needs to Learn to Multitask

As blockchain networks continue to mature, the conversation around scalability is changing. For years, the focus has largely been on increasing throughput and reducing transaction costs. Those metrics still matter, but they don’t tell the full story of what it takes to support applications at scale. Today’s blockchain networks are expected to support a much […]

Fundamentals
Cardamom 10.0.0: What to Expect

Cardamom 10.0.0: What to Expect

This blog post outlines the Rootstock Improvement Proposals (RSKIPs) proposed for inclusion in Rootstock’s next network upgrade and explains how you can make your voice heard.  Every Rootstock network upgrade is named after a plant rootstock symbolising how Rootstock allows new capabilities to grow from the foundations of the Bitcoin network. Past upgrades include Bamboo, […]

Ecosystem Updates
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