RSK Wasabi Release v1.2.0

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:
e3901dd011ee798559ee965186a4a54fdb2233acfd73bbe2e3164f66d821e661 rskj-core/build/libs/rskj-core-1.2.0-WASABI-all.jar

RSK Wasabi Release v1.1.0

IMPORTANT 1: In this release, we've made some changes to JSON-RPC methods to make them compliant to the Ethereum RPC API standard. One of the 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. Please be sure to make all necessary changes to your apps if required.

IMPORTANT 2: We're making the garbage collector feature available in what we call 'experimental mode'. We'll share more information about this, but be aware that it's not recommended to use it in production environments yet.

IMPORTANT 3: Our public nodes will serve rskj nodes version 1.0.2 by default for the next 30 days, unless the 1.1.0 version is specified. Afterwards, 1.1.0 version will become de default version. See our wiki for more information.

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 only) (#998).
• Added new RSK specific JSON-RPC methods including 'rsk_getRawBlockHeaderByHash', 'rsk_getRawTransactionReceiptByHash', among others (#1000).
• Security and bug fixing.

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

SHA256:
20a82720dd39864ae3603b7eb777ed454e4577c7d984b9560017fc4ddd820924 rskj-core-1.1.0-WASABI-all.jar

RSK Wasabi Release v1.0.2

This a patch release that contains a fix for an eth_call method corner case bug introduced in Wasabi 1.0.0, and also adds support for database migration in nodes that did not complete the upgrade to Wasabi before its activation in block number 1,591,000. For more details see:

• Workaround to build a repository for pending block execution (#931)
• Support unitrie migration after Wasabi activation (#941)

SHA256:
2fb6dcc0ab18e3c43a0f5073b1e11d514bd7ea74cd430e1e0bfca06d3126242a rskj-core-1.0.2-WASABI-all.jar

RSK Wasabi Release v1.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 RSK client node, we encourage you to update to this new version. The network upgrade will happen at block number 1,591,000.

IMPORTANT 2: Since the internal data structure is changing in this version, take into consideration that the first time you start your Wasabi node, it will do a migration process that can take up to 15 minutes. This is a one-time process, please pay attention to the information shown on screen indicating the result of the migration process.

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

• New state internal data structure (Unitrie) introduces important performance and storage improvements.
• New opcodes included in RSK virtual machine (create2, shr, shl).
• New RSK native contracts (blockHeader, getBTCTransactionConfirmations, …).
• New transaction debugging rpc method (debug_traceTransaction).
• Security improvements and bug fixes.

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

SHA256:
f67d4da176110b0b06e0684ecc5a341db189d17885c31ad8c0fe14992ab4f2f8 rskj-core-1.0.0-WASABI-all.jar

RSK Wasabi Release v1.0.0 Preview (Testnet only)

IMPORTANT: This is a Tesnet-only release. Since consensus rules have changed, this version is not compatible with previous versions. If you've been running previous versions of RSK client node in Testnet, we encourage you to update to this new version. See this blog post for more information.

A non-comprehensive list of changes to be included in the upcoming version is:

• New state internal data structure (Unitrie) introduces important performance and storage improvements.
• New opcodes included in RSK virtual machine (create2, shr, shl).
• New RSK native contracts (blockHeader, getBTCTransactionConfirmations, …).
• New transaction debugging rpc method (debug_traceTransaction).
• Security improvements and bug fixes.

You can find a complete list of the changes introduced in Wasabi 1.0.0 milestone, the definitive list of changes will be published when Wasabi 1.0.0 final version is released.

SHA256:
6b01a187cad148c3674b32515ac35450d32dc2959e7ed2460419ba1b8977054d rskj-core-1.0.0-PREVIEW-all.jar

RSK Orchid Release v0.6.2

This release contains performance improvements, storage requirements decrease and minor bug fixes. Several codebase refactors and cleanup are also part of this milestone. This is a summary of the changes included in this version:

• Codebase refactors and cleanup (#803, #796, #798, #792, #786)
• Decrease blockchain storage size (#793)
• Performance improvements in onchain logs retrieval (#795)
• Trie improvements (#789, #783, #782, #719, #778)
• Added new information to VM trace output (#785)
• Bug fixes in txpool module responses (#771)
• Other minor bug fixes (#801)

You can find a complete list of the changes introduced in Orchid 0.6.2 milestone.

SHA256:
90d8c45a044fd505b8c551b74376adb102b4bbd50f5e529337b71218198a535b rskj-core-0.6.2-ORCHID-all.jar

RSK Orchid Release v0.6.1

This is a patch release version that improves the peer discovery protocol handshake logic to prevent IP spoofing and traffic amplification attacks.

SHA256:
7b218742eabe2b477c5d0328d78983015f782f8023db12f1e3d1ec90e9db7927 rskj-core-0.6.1-ORCHID-all.jar

RSK Orchid Release v0.6.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. See this blog post for more information.

This release is mainly focused on Ethereum VM compatibility and bug fixing. This is a summary of the changes included in this version:

• RSK VM STATIC_CALL opcode has been aligned to Ethereum's implementation to enable support for Solidity 0.5.x contracts (Activated at Network Upgrade time)
• Added support for method eth_gasPrice
• Reported Websockets issue has been fixed (Github issue #700)

You can find a complete list of the changes introduced in Orchid 0.6.0 milestone.

SHA256:
a826a2f560fb85fad82d93532af4978f47e1cc0d1d25f2579380ca32e866aa58 rskj-core-0.6.0-ORCHID-all.jar

RSK Orchid Release v0.5.3

This release is mainly focused on bug fixing and security improvements. This is a summary of the changes included in this version:

• Add v, r and s EC values to JSON-RPC tx outputs (#661)
• Consider gas price for accepting tx pool replacements (#662)
• Improved disconnection collection recycling (#665)
• Don't close UDP channel on exception (#670)
• Unify contracts trie (#692)

You can find a complete list of the changes introduced in Orchid 0.5.3 milestone.

IMPORTANT: this release is mandatory for Testnet users and it's highly recommended that Mainnet nodes are also updated.

SHA256: 831c2a9f8717f3543bab985364c208defc46d8759867cf407cf39d7cdd371317 rskj-core-0.5.3-ORCHID-all.jar.

RSK Orchid Release v0.5.2

This release is only mandatory for users running RSK nodes on Testnet, it does not include any change from v0.5.1, it only changes Orchid block number activation for Testnet (starting at block 0).

IMPORTANT: if you are updating from a prior RSK version (v0.5.1 or earlier), you need to delete the files located in your node's database directory before starting your node (see database setting in your configuration file or look for content of default directory ${user.home}/.rsk/testnet/database).

SHA256: 33cc16404b7efb443a7625754f26477778601ed4a51c1930961fd3d934beee4c rskj-core-0.5.2-ORCHID-all.jar.