Skip to content
Back to Blog
Ecosystem Updates

RSK Fingerroot 5.3.0 is Here

Read Time: 2 mins
RSK Fingerroot 5.3.0 is Here

We are pleased to announce the release of the latest version of the RSKj Fingerroot client, now accessible in the RSKj GitHub repository. This update introduces several enhancements to the client’s JSON-RPC interface, along with notable improvements in performance and the resolution of a few non-critical bugs.

While this upgrade is optional, we strongly encourage users to update their nodes to the most recent version for an enhanced experience and to benefit from the latest improvements.

What changes are included in RSK Fingerroot 5.3.0?

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

  • Introducing support for `blockNumber` and `blockID` arguments in the `eth_estimateGas` JSON-RPC method in #2080.
  • Ignore replaced transactions in pending transactions gas cost calculations in #2105.
  • Fix the response format on the `eth_hashrate` JSON-RPC method in #2074.
  • Get rid of manual command-line arguments parsing and introduce `–help` and `–version` command-line flags using the Picocli framework in #2027.
  • Show the `rsk_protocolVersion` JSON-RPC method return value as hexadecimal in #2134.
  • Support the `input` field in JSON-RPC requests for compatibility with the Web3js framework library in #2075.
  • Increased receipts cache size and reduced blooms block size in #2127.

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

How do I upgrade to version 5.3.0?

There are no special considerations for upgrading to this version. Users are simply required to download and update their RSKj node; no additional tasks are necessary.

RSKj Fingerroot 5.3.0’s sha256 sum is a9d5c6080aecd96c849e153dd4648072323c772f860c0c4fd812a321fc18ae90 rskj-core-5.3.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.3.0. Please reach out on the 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

Bitcoin Miners Can Now Directly Participate in Rootstock Merge Mining Through DMND

Bitcoin Miners Can Now Directly Participate in Rootstock Merge Mining Through DMND

For the first time, Bitcoin miners can directly control their own Rootstock merge-mining commitments and receive rBTC rewards to their own address through DMND, a Stratum V2-first Bitcoin mining pool focused on miner sovereignty and decentralized mining infrastructure. Announced today by DMND and RootstockLabs, this marks a major evolution in Bitcoin mining infrastructure and an […]

Ecosystem Updates
Aori Integrates with Rootstock to Unlock Cross-Chain Bitcoin DeFi

Aori Integrates with Rootstock to Unlock Cross-Chain Bitcoin DeFi

The Bitcoin DeFi ecosystem continues to grow as new infrastructure connects it to the broader decentralized finance landscape. A new integration is now making it easier for users to move capital across chains while accessing Bitcoin-based financial applications. Aori is now live on Rootstock, introducing its intent settlement protocol to the Bitcoin smart contract ecosystem. […]

Ecosystem Updates
Vetiver 9.0.1: Patch Release

Vetiver 9.0.1: Patch Release

This patch release builds on the Vetiver 9.0.0 upgrade, which introduced multiple consensus improvements to enhance scalability, security, and performance across the network. Vetiver 9.0.1 introduces a fix for the debug_traceTransaction method, following issues reported by users after upgrading to Vetiver 9.0.0. Although Vetiver 9.0.1 is not a mandatory release, nodes that use the debug_traceTransaction […]

Ecosystem Updates