Skip to content
IRIS-3.1.0
Compare
Choose a tag to compare

This release contains several enhancements in JSON-RPC interface, Ethereum compatibility fixes and node performance improvements. This is a summary of the changes included in this version:

  • Added support for newPendingTransactions subscription (#1580)
  • Added support for EIP-1898: add blockHash to JSON-RPC methods which accept a default block parameter. (#1581)
  • Added support for debug_traceBlockByHash JSON-RPC method (#1546)
  • Added support for blockHash filter in eth_getLogs JSON-RPC method (#1527)
  • JSON-RPC compatibility fixes (#1491, #1522, #1564, #1588, #1601)
  • Performance improvements (#1459, #1557, #1569, #1579, #1585)

You can find a complete list of the changes introduced in Iris 3.1.0 milestone.

SHA256 (see Reproducible Build guide fo…

IRIS-3.0.1
9e3f884
Compare
Choose a tag to compare

This a patch release that contains a fix for a known issue where -under certain conditions- calls to the eth_getLogs method would return incorrect results (see issue #1600).

This is a non-mandatory upgrade, however we encourage users to upgrade to this version if they are running nodes used to retrieve blockchain event logs.

These are the changes included in this version:

  • Fix data retrieval for eth_getLogs method (#1605)
  • Ignore ‘type’ argument in JSON-RPC calls (#1606).

SHA256 (see Reproducible Build guide for further details):
a6223f3a9d289f1d5a4ab535b5e748f43b5829ab6274050b93f86d2c77223683 rskj-core-3.0.1-IRIS-all.jar

IRIS-3.0.0
ba01ea2
Compare
Choose a tag to compare

IMPORTANT: Since consensus rules have changed, this version is not compatible with previous versions. If you've been running previous versions of RSK client node, we encourage you to update to this new version. The Mainnet network upgrade will happen at block number 3,614,800. The Testnet network upgrade will happen at block number 2,060,500.

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

  • Add BLAKE2 compression function F precompile (RSKIP153)
  • Enable 2WP peg-in transactions to any RSK address (RSKIP170).
  • Flyover protocol consensus changes (RSKIP176).
  • BTC-RSK timestamp linking protection (RSKIP179).
  • Enable refunds for 2WP peg-out transactions with invalid amounts (RSKIP185)
  • Time-locked emergency multisignature…
PAPYRUS-2.2.0
5d4ad5c
Compare
Choose a tag to compare

This release contains relevant improvements from community feedback. Thanks to all RSK buidlers for your contributions!

This is a summary of the changes included in this version:

  • Add Content-Type field in JSON RPC responses (#1390)
  • Consider minimum gas price in eth_gasPrice method (#1389)
  • On-the-fly block blooms cache for faster events retrieval (#1384)
  • Fix v value in JSON RPC transaction result (#1382)

You can find a complete list of the changes introduced in Papyrus 2.2.0 milestone.

SHA256 (see Reproducible Build guide for further details):
f7cb1e6c5568332d047c602a5b2c464c41688336b824d92ef3a40b89a8f55b60 rskj-core-2.2.0-PAPYRUS-all.jar

PAPYRUS-2.1.0
Compare
Choose a tag to compare

This release contains performance improvements, bug fixes and security improvements. This is a summary of the changes included in this version:

  • Transaction relay improvements and handling of pending transactions fixes (#1266, #1134, #1253)
  • New persistent storage for logs bloom reduces execution times for eth_getLogs method (#1208)
  • New command-line tools enable local export and import of blocks (see this blog post for more info) (#1226)
  • Peer discovery now works for nodes behind NAT routers (#1262)
  • The eth_compile family of methods has been removed (#1211)
  • Other performance improvements (#1227, #1285)

You can find a complete list of the changes introduced in Papyrus 2.1.0 milestone.

SHA256 (see Reproducible Build guide for further details):

PAPYRUS-2.0.1
Compare
Choose a tag to compare

IMPORTANT 1: Some users reported that after upgrading to v2.0.0, they have experienced peer disconnections in their nodes. This release is a patch version to better handle timeout and peer disconnection scenarios. Please note that users running rskj Wasabi v1.3.0 don’t need to install rskj Papyrus v2.0.0 before installing this patch. Information below has been copied from v2.0.0 release, to be sure nobody misses it.

IMPORTANT 2: Since consensus rules have changed, this version is not compatible with previous versions. If you've been running previous versions of RSK client node, we encourage you to update to this new version. The Mainnet network upgrade will happen at block number 2,392,700. The Testnet network upgrade will happen at bloc…

PAPYRUS-2.0.0
e8c778d
Compare
Choose a tag to compare

IMPORTANT: Since consensus rules have changed, this version is not compatible with previous versions. If you've been running previous versions of RSK client node, we encourage you to update to this new version. The Mainnet network upgrade will happen at block number 2,392,700. The Testnet network upgrade will happen at block number 863,000.

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

  • Garbage Collector v0.2, includes improvements to the previously released garbage collection feature (beta version*).
  • Import sync v0.1 feature will let users sync their nodes in a fraction of the time currently required (beta version*)
  • Added support for segwit (P2SH-P2WPKH) peg-in transactions in RSK 2-way peg (after network upgrade acti…
WASABI-1.3.0
Compare
Choose a tag to compare

This release introduces the new JSON-RPC trace module with support to methods that provide users with transaction processing details. Please refer to RSK developers portal to understand how to configure your node to enable RPC modules.

This is a summary of the changes included in this version:

  • New trace_transaction JSON-RPC method (#1112)
  • New trace_block JSON-RPC method (#1112)
  • Performance improvements (#1173, #1174, #1175)

You can find a complete list of the changes introduced in Wasabi 1.3.0 milestone.

SHA256:
1343a100363d78db8c6563ec0778646b17af7fdaf7de2ac5932537582c079ddd rskj-core-1.3.0-WASABI-all.jar

WASABI-1.2.1
Compare
Choose a tag to compare

IMPORTANT: since rskj v1.2.1 includes security improvements, it is strongly recommended that all users update to this new version to avoid interruptions in their node's operations. In line with this, our public nodes offering JSON RPC services will serve rskj nodes version 1.2.1 with no support to previous versions.

This release improves block validation logic and enforces Armadillo checks by making this security feature part of the consensus rules. Armadillo adds additional information to RSK merge-mining tags so that users or automated systems can make informed decisions about the network health. More information about Armadillo can be found here.

SHA256: 63ecedbfc52d0738495048be2cee214ee3d12f021ba4e256b903e9f02f4ee84a rskj-core/build/…

WASABI-1.2.0
ba81943
Compare
Choose a tag to compare

IMPORTANT: since rskj v1.2.0 includes security improvements, it's strongly recommended that all users update to this new version to avoid interruptions in their node's operations. In line with this, our public nodes offering JSON RPC services will serve rskj nodes version 1.2.0 with no support to previous versions.

This release contains performance improvements, Ethereum compatibility fixes and security improvements. This is a summary of the changes included in this version:

  • Ethereum compatibility fixes in logs (#1108)
  • Concurrent operations improvements (#1109, #1116)
  • Several security improvements

You can find a complete list of the changes introduced in Wasabi 1.2.0 milestone.

SHA256:
e3901dd011ee798559ee965186a4a54fdb2233acfd73bbe2e3…