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
getActivePowpegRedeemScriptto 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
accountSlotsconfig (#1763) - Disable
sco,debug, andtracerpc 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