RSK Hop Release v4.0.0

IMPORTANT 1: since consensus rules have changed, this version is not compatible with previous versions. If you've been running previous versions of the RSK client node, we encourage you to update to this new version. The Mainnet network upgrade will happen at block number 4,598,500. The Testnet network upgrade will happen at block number 3,103,000.

IMPORTANT 2: this release makes the sco, debug, and trace JSON-RPC modules disabled by default. For security reasons, it is suggested to have these modules enabled only when needed. Node operators that use any of these modules must consider this and enable them in their config files. See the Node Configuration Reference page in the RSK Developers' Portal for details on RSK node configuration.

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

• Bridge peg-out batching (RSKIP-271)
• New deserialization method for Flyover refund addresses (RSKIP-284)
• Adjust minimum block difficulty on Testnet (RSKIP-290)
• Add method getActivePowpegRedeemScript to the Bridge contract and perform additional Flyover peg-in validations (RSKIP-293)
• Limit the number of inputs to include in a migration transaction (RSKIP-294)
• Increase max timestamp difference between BTC and RSK blocks for Testnet (RSKIP-297)
• Increased accountSlots config (#1763)
• Disable sco, debug, and trace rpc modules by default (#1757)

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

SHA256 (see Reproducible Build guide for further details): 69c5c385986400bebdb2b57406bdb27ba1c19fa7e095000e56ec3a521e86352e rskj-core-4.0.0-HOP-all.jar

RSK Iris Release v3.3.0

This release contains several enhancements in JSON-RPC interface, Ethereum compatibility fixes and node robustness enhancements. This is a non-comprehensive list of the changes included in this version:

• Fix web3_sha3 method for non-hex encoded strings in #1637
• JSON-RPC compatibility fixes in #1659
• eth_getLogs method performance improvements in #1650
• Mitigated db inconsistency issue after improper node shutdown in #1660
• Enabled fast block propagation mode by default in #1677
• Added tracing options to debug_traceTransaction method in #1644

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

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

RSK Iris Release v3.2.0

IMPORTANT: RSK Testnet consensus rules have changed in this version, and it is not compatible with previous versions (only for Testnet, this doesn't apply to Mainnet). If you've been running previous versions of the RSK client node in Testnet, we encourage you to update to this new version. The Testnet network upgrade will happen at block number 2,581,800. This is a non-mandatory upgrade for RSK Mainnet nodes.

This release contains enhancements to the node's JSON-RPC interface, as well as Ethereum compatibility fixes. It also introduces a consensus change for Testnet that increases the minimum block difficulty and avoids scenarios where a huge number of blocks would be mined in a short period of time if the difficulty dropped to the minimum levels (doesn't apply to Mainnet).

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

• Improved message queue expiration policy (#1610)
• Added support for pending parameter in eth_getBlockByNumber JSON-RPC method (#1627)
• JSON-RPC compatibility fixes (#1623, #1629)
• Fixed eth_isSyncing method which was not working as expected (#1618)
• Introduced gas exactimation enhancements to the eth_estimateGas method (#1548)
• Mining rate limiting and updated minimum block difficulty for RSK Testnet (#1615, #1671)

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

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

RSK Iris Release v3.1.0

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 for further details):
07dea8cd7b80e1341c06e1c9f6d15f2b381f5d46443db777ebded194088a5784 rskj-core-3.1.0-IRIS-all.jar

RSK Iris Release v3.0.1

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

RSK Iris Release v3.0.0

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 (RSKIP201).
• Reduced 2WP peg-in and peg-out minimum amounts (RSKIP219).
• Open Bitcoin blockchain oracle (RSKIP220).

These are the most relevant non-consensus improvements included in this version:

• Improvements and compatibility fixes at the JSON-RPC interface (#1481, #1482, #1483, #1451, #1352, #1299, #1339, #1284)
• New rewind feature added to CLI tool (#1443)
• Block propagation enhancements (#1326)
• Node performance improvements (#1327)
• Use native library for recovery signature (#1258)
• Add Java11 support (#1252)

For a detailed description of the consensus changes introduced in this network upgrade, please refer to RSKIP 187 Network Upgrade: Iris. You can also find a complete list of the changes introduced in Iris 3.0.0 milestone.

SHA256 (see Reproducible Build guide for further details):
8c975d8489599dbe551e90f96b450ec8a2589385c3176e4ce6ced9d44b09782b rskj-core-3.0.0-IRIS-all.jar

RSK Papyrus Release v2.2.0

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

RSK Papyrus Release v2.1.0

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):
ecc4163c5292cef3b72580f07cfa30dae3996a95fc426ea09766a71e07d58918 rskj-core-2.1.0-PAPYRUS-all.jar

RSK Papyrus Release v2.0.1

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 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 activation).
• Additions to the 2WP process (locking cap and improvements to the return of funds logic) in preparation to the whitelisting mechanism removal (after network upgrade activation).
• Added support for logs subscription in eth_subscribe JSON RPC method.
• Added ECADD, ECMUL and PairingCheck precompiled contracts (after network upgrade activation).
• Added CHAINID, SELFBALANCE and EXTCODEHASH opcodes (after network upgrade activation).

(*) These features are still in beta, meaning they are not yet reliable to be used in a production environment and are disabled by default. Please refer to RSK Developer Portal for further information.

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

For a detailed description of the consensus changes introduced in this network upgrade, please refer to RSKIP 141 Network Upgrade: Papyrus.

SHA256:
43149abce0a737341a0b063f2016a1e73dae19b8af8f2e54657326ac8eedc8a0 rskj-core-2.0.1-PAPYRUS-all.jar

RSK Papyrus Release v2.0.0

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 activation).
• Additions to the 2WP process (locking cap and improvements to the return of funds logic) in preparation to the whitelisting mechanism removal (after network upgrade activation).
• Added support for logs subscription in eth_subscribe JSON RPC method.
• Added ECADD, ECMUL and PairingCheck precompiled contracts (after network upgrade activation).
• Added CHAINID, SELFBALANCE and EXTCODEHASH opcodes (after network upgrade activation).

(*) These features are still in beta, meaning they are not yet reliable to be used in a production environment and are disabled by default. Please refer to RSK Developer Portal for further information.

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

For a detailed description of the consensus changes introduced in this network upgrade, please refer to RSKIP 141 Network Upgrade: Papyrus.

SHA256:
83dc18fff337848a4ea9dfc9e07c0cf51f7a5cb34d0a5767961164a71f2f4d9b rskj-core-2.0.0-PAPYRUS-all.jar