Skip to content

v1.30.0
Compare
Choose a tag to compare
@kamilchodola kamilchodola released this 11 Dec 13:48
1.30.0
7bd28c7

Release Notes

⚠️ We highly recommend using v1.30.1 instead

Major Highlights

Gas limit increase

The recent update increases the default gas limit from 30MGas to 36MGas, reflecting the current pre-Pectra safe limit; as identified by EF Research1 and tested on the Sepolia testnet, while ensuring compatibility with consensus layer clients. This adjustment is designed to improve transaction throughput and overall network efficiency.

To ensure the new default value is applied, do one of these:

  • Remove the Blocks.TargetBlockGasLimit configuration option if any
  • Explicitly set it to 36000000.

If maintaining the previous gas limit is necessary, you can override the default by setting the following configuration option:

--Blocks.TargetBlockGasLimit 30000000

This approach provides flexibility while optimizing for evolving network demands and the rising asset price for the gas token.

Gnosis shutterized transactions

Shutter, a cutting-edge privacy solution leveraging threshold cryptography, is now officially supported in Nethermind 1.30.0. Initially enabled for a selected group of validators, it is now available for everyone. Shutter encrypts transactions in the mempool, keeping transaction details private until finalized on-chain. This ensures protection against frontrunning and supports fair and secure transaction execution on the Gnosis Chain.

Enabling Shutter in Nethermind:

  1. Update to Nethermind 1.30.0

  2. Generate validator registration files by following the instructions in Shutter Validator Registration repository

  3. Configure Nethermind as follows:

    --Shutter.Enabled true
--Shutter.ValidatorInfoFile /data/execution/validatorInfo.json

  4. Run Nethermind with the updated configuration to enable Shutter functionality.

Gigagas performance

image

We introduced several significant performance enhancements that substantially boosted tip-of-chain processing times. These improvements enabled us to achieve an impressive average processing throughput of 1 Gigagas/s, as recorded on the Base Mainnet chain.

One of the most impactful changes was optimizing and parallelizing in-memory pruning. This process is now significantly faster and no longer interferes with the block processing thread, reducing the likelihood of block processing spikes.

New supported chains

We added support for two new L2 networks: Taiko and Linea. To start with these networks, use the command below configurations:

  1. taiko-mainnet
  2. taiko-hekla
  3. linea-mainnet
  4. linea-sepolia

Additionally, as part of the preparation for Pectra hard-fork, we added support for the Mekong testnet. To run it, use -c mekong and ensure the respective consensus client version is running alongside.

Optimism improvements

For the Optimism implementation, we introduced support for the new hard-fork, Holocene, which took place on the Sepolia chains.

Additionally, we enabled our AutoPivot mechanism for new nodes starting synchronization. This significantly reduces the duration of the initial sync stage for OP and Base nodes, cutting the total sync time by approximately 30–60 minutes.

CLI updates

As a part of our efforts following Posix CLI conventions for our command line options, we introduced all lowercase dash-separated alternatives for all Nethermind command line options. For instance, --JsonRpc.JwtSecretFile can be spelled as --jsonrpc-jwtsecretfile or --Metrics.Enabled as --metrics-enabled.
Some option names have been deprecated (while still supported with a warning) in favor of new ones. For instance, -dd, --datadir is deprecated in favor of --data-dir.

Also, Nethermind configuration files now have a .json extension instead of the previous .cfg one. While this should not cause any issues for our users, we highly recommend not using extensions when specifying config names – always prefer -c mainnet over -c mainnet.json, or -c mainnet.cfg. Note that this does not apply to the cases when the -c option specifies a path, e.g. -c path/to/mainnet.json.

For more info, see configuration docs.

Changelog

New features

Pectra

New chains

Performance

4444

  • Receipts: Add option to not recover sender and write flags by @asdacap in #7680

Shutter

Optimism

Bug fixes and stability

Logging

Other changes

New Contributors

Full Changelog: 1.29.1...1.30.0

  1. Eth Research: On Increasing the Block Gas Limit: Technical Considerations & Path Forward ↩

Contributors

rubo, flcl42, and 18 other contributors
Assets 8
Loading