RSK Fingerroot Release v5.1.0

Summary

This update brings additions and enhancements to the JSON-RPC API and security and performance improvements. Although this upgrade is not mandatory, we highly recommend that users upgrade their nodes to the latest version.

What's New in RSKj 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 the node’s databases to disk without interrupting the node in #1856.
• Allow specifying VM options when running RSKj in a docker container in #1998.

Full Changelog: FINGERROOT-5.0.0...FINGERROOT-5.1.0

Fingerroot 5.1.0 Milestone: https://github.com/rsksmart/rskj/milestone/36

New Contributors

• @ivanIOV made their first contribution in #2011

Reproducible Build

SHA256 (see Reproducible Build guide for further details):
0c0707d01d14c7bef5a53407aace8b2a637d42964f9847b14aa38e2088e5cf3b rskj-core-5.1.0-FINGERROOT-all.jar

RSK Fingerroot Release v5.0.0

IMPORTANT: since consensus rules have changed, this version is incompatible with previous versions. If you've been running earlier versions of the RSK client node, we encourage you to update to this new version. The Mainnet network upgrade will happen at block number 5,468,000. The Testnet network upgrade will happen at block number 4,015,800.

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

• Transaction gas price cap (RSKIP-252)
• Peg-out events improvements (RSKIP-326)
• Reestablish the number of block confirmations for a PowPeg migration period (RSKIP-374)
• Use the pegout creation transaction hash as the key in the map structure that stores the pegout transactions waiting for signatures (RSKIP-375)
• Store the last retired PowPeg standard P2SH script (RSKIP-377)
• Increase POWpeg activation age (RSKIP-383)
• Bridge method getEstimatedFeesForNextPegOutEvent improvement (RSKIP-385)

For a detailed description of each consensus change introduced in this network upgrade, please refer to RSKIP 388 - Network Upgrade: Fingerroot. You can also find a complete list of the changes introduced in the corresponding GitHub milestone.

SHA256 (see Reproducible Build guide for further details): 198d13a8676714f289e5707dba3f45c6c2dbc5daa1a08c669e64a41df2fe330a rskj-core-5.0.0-FINGERROOT-all.jar

RSK Hop Release v4.4.0

Summary

This update brings performance enhancements, JSON RPC methods improvements, and Ethereum compatibility fixes. Although this upgrade is not mandatory, we highly recommend that users upgrade their nodes to the latest version.

What's New in RSKj 4.4.0

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

• Support named arguments in node’s CLI tools in #1893
• Added JSON RPC timeouts & transaction gas cap limit validations in #1954
• Improved eth_getLogs JSON RPC method performance in #1985
• Enable cache.states.persist-snapshot setting by default in #1980
• Included the type field in tx receipts and tx result responses for Ethereum libraries compatibility in #1984

Full Changelog: HOP-4.3.0...HOP-4.4.0

Hop 4.4.0 Milestone: https://github.com/rsksmart/rskj/milestone/34

Reproducible Build

SHA256 (see Reproducible Build guide for further details):
10e82f9e4fc80487f0e0799c4082275c2360e243d12fd791cb5108a05a71f7f8 rskj-core-4.4.0-HOP-all.jar

RSK Hop Release v4.3.0

Summary

This update brings a host of crucial security improvements, including the activation of peer scoring and virtual gas features by default, and the adoption of the most recent stable versions of various libraries used by the client node. Although this upgrade is not mandatory, we highly recommend that users upgrade their nodes to the latest version.

What's New in RSKj 4.3.0

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

• Update netty by @rmoreliovlabs in #1879
• Openrpc doc by @illuque-iov in #1839
• Junit5 update by @illuque-iov in #1878
• Upgrade jackson and jsonrpc libs by @rmoreliovlabs in #1883
• Updated log for forced virtual gas subtraction by @illuque-iov in #1913
• Signature cache by @nagarev in #1876
• Add CodeQL workflow for GitHub code scanning by @Vovchyk in #1953
• Rewind fixes by @illuque-iov in #1939
• Not dispose Options instance in RocksDbDataSource until db is closed by @casiojapi in #1947
• Validating transaction signature for send transaction methods by @rmoreliovlabs in #1941
• Adding Correlation id to the logs by @asoto-iov in #1906
• Add constraints to request payload by @rmoreliovlabs in #1914
• Enable rate limit and peer scoring features by default by @casiojapi in #1960
• Sets default locale when converting numbers to strings in FormatUtils by @javicid in #1710

Full Changelog: HOP-4.2.0...HOP-4.3.0

Hop 4.3.0 Milestone: https://github.com/rsksmart/rskj/milestone/33

New Contributors

• @casiojapi made their first contribution in #1947

Reproducible Build

SHA256 (see Reproducible Build guide for further details):
10553c20d2cffd4138eda56afa584a99019a903526da3e1de7029e8858f211af rskj-core-4.3.0-HOP-all.jar

RSK Hop Release v4.2.0

Summary

This release includes support for running RSKj on ARM processors, compatibility with Java 17, and fixes for JSON-RPC issues, among other things. Additionally, some features, such as Peer Scoring and support for RocksDB storage library, are now considered production-ready. Although this upgrade is not mandatory, we highly recommend that users upgrade their nodes to the latest version.

What's New in RSKj 4.2.0

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

• Introduced a command-line interface tool to migrate between LevelDb and RocksDb storage libraries in #1834. See Rootstock Developers Portal for more information.
• Added support for ARM CPUs on Linux OS in #1892. It requires using the RocksDb storage library.
• Allow wildcard to hosts config to accept all hosts in #1800.
• Fixed issue with eth_call JSON-RPC method when executed for a pending block in #1915.
• Added support for Java 17 in #1812.

In addition, the following features, previously marked as experimental, are now considered production-ready but yet disabled by default in this version:

• Added support for RocksDb storage library in #1703. See Rootstock Developers Portal for more information.
• Introduced a new peer reputation system in #1737, #1739, #1740, #1745, #1750, #1772, and #1782.
• Introduced a transaction rate limiter preventing the consumption of a large amount of resources in #1749 and #1806.

You can find a complete list of the changes introduced in Hop 4.2.0 milestone.

Full Changelog: HOP-4.1.1...HOP-4.2.0

Reproducible Build

SHA256 (see Reproducible Build guide for further details):
556132bb0423f0ca0a101704d56daad17eaa124d4f88cf97ced8ca7ebcddb0b2 rskj-core-4.2.0-HOP-all.jar

RSK Hop Release v4.1.1

Summary

This release introduces remediation to the peg-out service issue in RSK Mainnet, as described here. However, the peg-out service will resume operations when the PowPeg address is updated, and the new redeem script activated (date not defined yet, will be announced soon).

Since consensus rules have changed, this version is incompatible with earlier versions. Consequently, if you adhere to these changes, you must upgrade to the new client version before the network upgrade is activated. Otherwise, the non-updated nodes will remain on an incompatible chain. The Mainnet network upgrade will happen at block number 4,976,300.

We encourage you to upgrade to this new version if you are running version 4.1.0 of the RSK client node. If you are running version 4.0.0 of the RSK client node in Mainnet, we recommend upgrading to this version instead.

What's New in RSKj 4.1.1

The consensus changes included in this version are:

• Align RSK P2SH redeem script with Bitcoin Core standard transactions checks (RSKIP-353)
• Adjust the number of block confirmations for a PowPeg migration period (RSKIP-357)

For a detailed description of each consensus change introduced in this network upgrade, please refer to RSKIP 358 Network Upgrade (patch): Hop 4.0.1. You can also find a complete list of the changes introduced in the corresponding GitHub milestone.

Full Changelog: HOP-TESTNET-4.1.1...HOP-4.1.1

Reproducible Build

SHA256 (see Reproducible Build guide for further details): c71b644e6080e7e1b42b34b075f51ee37de49ab956282e51ca5f115d73a90c1f rskj-core-4.1.1-HOP-all.jar

RSK Hop Release v4.0.1

Summary

This release introduces remediation to the peg-out service issue in RSK Mainnet, as described here. However, the peg-out service will resume operations when the PowPeg address is updated and the new redeem script activated (date not defined yet, will be announced soon).

Since consensus rules have changed, this version is incompatible with earlier versions. Consequently, if you adhere to these changes, you must upgrade to the new client version before the network upgrade is activated. Otherwise, the non-updated nodes will remain on an incompatible chain. The Mainnet network upgrade will happen at block number 4,976,300.

We encourage you to upgrade to this new version if you are running version 4.0.0 of the RSK client node. If you are running version 4.1.0 of the RSK client node in Mainnet, we recommend upgrading to this version instead.

What's New in RSKj 4.0.1

The consensus changes included in this version are:

• Align RSK P2SH redeem script with Bitcoin Core standard transactions checks (RSKIP-353)
• Adjust the number of block confirmations for a PowPeg migration period (RSKIP-357)

For a detailed description of each consensus change introduced in this network upgrade, please refer to RSKIP 358 Network Upgrade (patch): Hop 4.0.1. You can also find a complete list of the changes introduced in the corresponding GitHub milestone.

Full Changelog: HOP-TESTNET-4.0.1...HOP-4.0.1

Reproducible Build

SHA256 (see Reproducible Build guide for further details): 0ed5aa42ba590be6d4947ac48362af57e46f4f228d554a1c26f79e84a0784dc1 rskj-core-4.0.1-HOP-all.jar

RSK Hop Testnet Release v4.1.1 (Testnet-only version)

Summary

This Testnet-only release fixes the peg-out service issue as described here. This release will serve as a final confirmation for the fix before moving forward with the Mainnet patch release. Since consensus rules have changed, this version is incompatible with previous versions. The Testnet network upgrade will happen at block number 3,362,200.

If you are running version 4.1.0 of the RSK client node in Testnet, we encourage you to upgrade to this new version. If you are running version 4.0.0 of the RSK client node in Testnet, we recommend upgrading to this version instead.

What's New in RSKj Testnet 4.1.1

The consensus changes included in this version are:

• Align RSK P2SH redeem script with Bitcoin Core standard transactions checks (RSKIP-353)
• Adjust the number of block confirmations for a PowPeg migration period (RSKIP-357)

For a detailed description of each consensus change introduced in this network upgrade, please refer to RSKIP 358 Network Upgrade (patch): Hop 4.0.1. You can also find a complete list of the changes introduced in the corresponding GitHub milestone.

Full Changelog: HOP-4.1.0...HOP-TESTNET-4.1.1

Reproducible Build

SHA256 (see Reproducible Build guide for further details): 6999deb8b6266cd64e2f408bf3b748904348083f6a678b92cf7b43223f643d6c rskj-core-4.1.1-HOP-TESTNET-all.jar

RSK Hop Testnet Release v4.0.1 (Testnet-only version)

Summary

This Testnet-only release fixes the peg-out service issue as described here. This release will serve as a final confirmation for the fix before moving forward with the Mainnet patch release. Since consensus rules have changed, this version is incompatible with previous versions. The Testnet network upgrade will happen at block number 3,362,200.

If you are running version 4.0.0 of the RSK client node in Testnet, we encourage you to upgrade to this new version. If you are running version 4.1.0 of the RSK client node in Testnet, we recommend upgrading to this version instead.

What's New in RSKj Testnet 4.0.1

The consensus changes included in this version are:

Align RSK P2SH redeem script with Bitcoin Core standard transactions checks (RSKIP-353)
Adjust the number of block confirmations for a PowPeg migration period (RSKIP-357)

For a detailed description of each consensus change introduced in this network upgrade, please refer to RSKIP 358 Network Upgrade (patch): Hop 4.0.1. You can also find a complete list of the changes introduced in the corresponding GitHub milestone.

Full Changelog: HOP-4.0.0...HOP-TESTNET-4.0.1

Reproducible Build

SHA256 (see Reproducible Build guide for further details): 1dfb2936f7ae0d8bad51607c1df18a9ad370a28ba99cae4e27cb4c13a6116719 rskj-core-4.0.1-HOP-TESTNET-all.jar

RSK Hop Release v4.1.0

Summary

This release brings new JSON-RPC tracing methods, support for the latest versions of Hardhat development environment, the introduction of a peer reputation system, and support for RocksDb storage library, among other things. While this is a non-mandatory upgrade, we encourage users to upgrade their nodes to the new version.

What's New in RSKj 4.1.0

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

• Introduced a new peer reputation system in #1737, #1739, #1740, #1745, #1750, #1772, and #1782 [experimental].
• Introduced two new JSON-RPC tracing methods: trace_get and trace_filter in #1711, and #1744.
• Added support for RocksDb storage library in #1703 [experimental]. See RSK Developers Portal for more information.
• Fixed corner case bug in eth_estimateGas JSON-RPC method in #1803.
• Accept websocket connections without requiring the websocket suffix in the URL path in #1753.
• Improved the eth_gasPrice method by fetching historical gas prices from DB at node startup in #1724.
• Added Content-Length and Connection headers to JSON-RPC responses, solving issues Hardhat users had when interacting with RSKj, in #1836.

You can find a complete list of the changes introduced in Hop 4.1.0 milestone.

Full Changelog: HOP-4.0.0...HOP-4.1.0

NOTE: features marked as [experimental] are disabled by default. They require further validation and should only be used with caution. They can be changed or removed in future releases of the node. If you don't know what these features are or their possible impact, you likely should not enable them.

Reproducible Build

SHA256 (see Reproducible Build guide for further details):
d5ec4c766b184d13dde8c4cdef6f30481731b72c562c087bfd0c223d5709a2e6 rskj-core-4.1.0-HOP-all.jar