Wasabi Release v1.1.0 Is Here

We’re pleased to announce that a new RSK Wasabi release has been published in our Github repo. This a minor release mostly focused on improvements at the JSON-RPC API interface: we’ve added support to previously unsupported methods and parameters, and we’ve made some minor changes to make JSON-RPC responses compliant with the Ethereum RPC API standard.

What’s new in this release?

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

Added JSON-RPC method ‘eth_chainId’ (#945).
Added support for ‘pending’ parameter in ‘eth_getCode’ JSON-RPC method (#970).
Several minor improvements to JSON-RPC responses to make them Ethereum RPC API standard compliant (#934, #958, #971).
Garbage collector (experimental version) (#998).
Added new RSK specific JSON-RPC methods including ‘rsk_getRawBlockHeaderByHash’, ‘rsk_getRawTransactionReceiptByHash’, among others (#1000).
Security and b ug fixing.

Version 1.1.0 release’s sha256 sum is 20a82720dd39864ae3603b7eb777ed454e4577c7d984b9560017fc4ddd820924 rskj-core-1.1.0-ORCHID-all.jar. See Reproducible Build guide for further details.

How can the JSON-RPC interface changes can affect my dApps?

In this release, we’ve made some changes to JSON-RPC methods to make them compliant to the Ethereum RPC API standard. One of these requirements is that all quantities need to be expressed in hex format. Prior to this version, the ‘minimumGasPrice’ was being wrongly returned in decimal format. Before you update your RSK node to this new version, please be sure to make all necessary changes to your apps to adjust to this change.

With the objective of not breaking existing integrations, as part of this release we are also deploying a versioning feature to our public nodes. For a fixed period of time, the root url https://public-nodes.rsk.com will resolve to the RSKj 1.0.2 version nodes, while you can access 1.1.0 public nodes specifying this release version as part of the url: https://public-nodes.rsk.com/1.1.0/. Please refer to our documentation to understand better how this versioning schema works.

More information about the Garbage Collector feature

This is a new component that enables the node to split the state trie storage into multiple databases and claim old data that is unlikely to be needed in the future. Node administrators will be able to set their own retention policies to ensure they have access to everything they need for their operations.

The version we’re releasing has some known limitations, but we still wanted to make it available for anyone willing to try it at this experimental stage:

This feature is still being tested and is not recommended for production.
The node may exhibit unexpected behavior when querying collected states (e.g eth_getBalance with an old block number).
Disabling the garbage collector will cause the node to re-synchronize from start.

If you understand the risk associated with running beta software and want to try it out, you have to set the configuration variable blockchain.gc.enabled to true. You will see a new set of directories (database/unitrie_0, database/unitrie_1…) in your database directory. And specially, you will notice that the combined size of these repositories is much smaller than the current database/unitrie!