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 version of the RSKj client is now available for download from the RSKj GitHub repository.
What changes are included in Vetiver 9.0.3?
A non-exhaustive list of changes included in this release is provided below:
- Fix incorrect calldata for sub-calls in trace_transaction and trace_block, by italo-sampaio in #3546.
- Fix commitHash value for docker images, by fmacleal in #3560.
- Set default limits for the eth_getLogs method, by wlaclaw in #3475.
You can find a complete list of the changes introduced in the corresponding GitHub milestone.
Is there anything I need to consider when upgrading to Vetiver 9.0.3?
RSK nodes that rely on these tracing methods should be updated to this version to avoid potential issues. Other than that, there are no other special considerations beyond updating your node to the latest version.
RSKj Vetiver 9.0.3’s sha256 sum is b15fbccb9b1aa2cec082f6f68beeed23cbbcfcf1caf5d0099e4ad146e72b2135 rskj-core-9.0.3-VETIVER-all.jar.
See the Reproducible Build guide for further details.
How do I report security vulnerabilities?
If you find a security issue, please contact us at security@rootstocklabs.com or report it through RootstockLabs’ bug bounty program. We reward security experts, software developers, and hackers who dedicate time and effort to improving and protecting the Rootstock platform.
Do you have further questions?
Please contact 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.
Website | Twitter | Developer Portal | Discord | Youtube | Blog
