Skip to content
Back to Blog
Ecosystem Updates

RSK Fingerroot 5.1.0 is Here

Read Time: 1 mins
RSK Fingerroot 5.1.0 is Here

We are excited to unveil the latest version of the RSKj Fingerroot client, now available in the RSKj GitHub repository. This update brings additions and enhancements to the JSON-RPC API, as well as security and performance improvements.

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

What changes are included in RSK Fingerroot 5.1.0?

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

  • Fixed issues with the evm_reset JSON-RPC method in #2024.
  • Introduced configurable limits for the eth_getLogs JSON-RPC method in #2035.
  • Introduced configurable limit for JSON-RPC responses size in #1997.
  • New rsk_flush JSON-RPC method lets users flush node’s databases to disk without interrupting the node in #1856.
  • Allow specifying VM options when running RSKj in a docker container in #1998.

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

How do I upgrade to version 5.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 Fingerroot 5.1.0’s sha256 sum is 0c0707d01d14c7bef5a53407aace8b2a637d42964f9847b14aa38e2088e5cf3b rskj-core-5.1.0-FINGERROOT-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 Fingerroot 5.1.0. Please reach out on Rootstock Discord Server 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 Discord Server 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

Discord: https://discord.gg/rootstock-842021106956238848

Telegram: https://t.me/rskofficialcommunity

Recommended articles

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
Vetiver 9.0.2: Patch Release

Vetiver 9.0.2: Patch Release

This patch release fixes an issue reported by users after upgrading to Vetiver 9.0.0, which prevents some Testnet nodes from successfully completing a full blockchain synchronization, especially after a node restart. It also introduces minor performance and security improvements. Although this is not a mandatory release, Testnet nodes should be updated to this version to […]

Ecosystem Updates
Introducing Atlas: The easiest way in to BTCFi

Introducing Atlas: The easiest way in to BTCFi

Most Bitcoin today is held, not actively used. Not because there’s no demand, but because using Bitcoin beyond holding is complex, costly, and dependent on intermediaries where tradeoffs around trust, cost, and control aren’t always clear. Borrowing against BTC or generating yield has traditionally required navigating fragmented infrastructure, comparing bridges, and making routing and security […]

Ecosystem Updates