Skip to content
Back to Blog
Ecosystem

Rootstock Arrowhead6.5.0: Optimizing DeveloperExperience

Read Time: 2 mins
Rootstock Arrowhead 6.5.0: Optimizing Developer Experience

The Rootstock community is pleased to announce the release of the latest version of the RSKj client, which is now available in the RSKj GitHub repository. This update features new debugging methods and other improvements to the JSON-RPC interface, designed to optimize the developer experience.

Although this upgrade is optional, it is strongly recommended that users update their nodes to the latest version to benefit from enhanced performance and security.

What changes are included in RSK Arrowhead 6.5.0?

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

  • Added the debug_traceBlockByNumber RPC method, by @Vovchyk in #2809.
  • Added support for the callTracer trace in the debug_traceTransaction, debug_traceBlockByHash, and debug_traceBlockByNumber RPC methods, by @asoto-iov in #2839.
  • Added support for null values in the to and from input parameters of RPC methods, by @Vovchyk in #2868.
  • Handle reverted transactions in the eth_estimateGas method to align with Ethereum client behavior, by @rmoreliovlabs in #2846.

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

How do I upgrade to version 6.5.0?

Starting with the previous release of RSKj, Java 17 (LTS) has become the minimum supported version, and previous versions of Java will no longer be supported. Node operators upgrading from a version before 6.4.0 should upgrade to a compatible Java version to ensure continued functionality. Upgrading to this version requires no other considerations. 

RSKj Arrowhead 6.5.0’s sha256 sum is 294f99ec76befa7d9ef18eca28d0c884ceb463ce855ef23ddb7a476e551ba191 rskj-core-6.5.0-ARROWHEAD-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 running Arrowhead 6.5.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@rootstocklabs.com or report it through the RootstockLabs’ 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 contact the core team through the 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:

Website | X | Developer Portal | Discord | Youtube | Blog

Recommended articles

Arrowhead 6.5.1: Patch Release

Arrowhead 6.5.1: Patch Release

The Rootstock community is pleased to announce the release of the latest version of the RSKj client, which is now available in the RSKj GitHub repository. This patch release reverts the JDK and JRE versions used in the Docker container from Java 21 to Java 17 due to synchronization issues encountered with the latest update. […]

Ecosystem
POWpeg App v2.3: The Safest Bitcoin Bridge is Now 50x Faster

POWpeg App v2.3: The Safest Bitcoin Bridge is Now 50x Faster

Bringing your Bitcoin into Rootstock where it can be used to participate in the Bitcoin DeFi economy just got a major upgrade.  Rootstock’s native bridge, the POWpeg has been the unstoppable, uncensorable, and unbreakable Bitcoin bridge in existence since launching in 2018 and  as of today it is now 50x faster, jumping from 16 hours […]

Ecosystem
Bringing Fiat to Rootstock: A Guide to Getting rBTC

Bringing Fiat to Rootstock: A Guide to Getting rBTC

The growth of Bitcoin DeFi has seen remarkable progress, with $6.6 billion of Bitcoin locked in DeFi protocols as of Feb 2025. And with Rootstock being the home of DeFi on Bitcoin, it is important to understand how you can access rBTC, the native token of Rootstock used to navigate the opportunities in the ecosystem.  […]

Users