Skip to content

v1.25.4

Compare
Choose a tag to compare
@kamilchodola kamilchodola released this 16 Feb 18:35

Release notes

⚠️

This release is a mandatory upgrade for all nodes operating on the Ethereum Mainnet and Gnosis.
Please update your node to this version to ensure correct node functionality.

Major highlights

Mainnet Dencun hard fork

The Mainnet Dencun hard fork is scheduled on Mar 13, 2024 at 13:55:35 UTC (epoch 269568)
⚠️ Execution client and consensus client database sizes can increase by about 150GB over time - please prepare for that!

Gnosis Dencun hard fork

The Gnosis Dencun hard fork is scheduled on Mar 11, 2024 at 18:30:20 UTC (slot 14237696)
⚠️ Execution client and consensus client database sizes can increase by about 150GB over time - please prepare for that!

PPA package

The PPA package has been revised, including the version and installers. Since the version has been fixed to be 1.25.4 instead of 1.2540, installing the latest version requires the manual removal of the previous one as follows:

# ⚠️ If your data directory is in the default location of /usr/share/nethermind, back it up before the package removal.

sudo apt-get purge -y nethermind
sudo apt-get update

Changelog

Cancun

Optimism

  • Add temporary solution for pre-bedrock tx decoding by adding AncientBarriers by @deffrian in #6620

Bugfixes and new features

  • Reduce default peers amount from 100 to 50 on mainnet nodes (not on archive nodes) to reduce a load on it and reduce amount of block processing spikes in #6743
  • Reduce amount of hanging sockets with TIME_WAIT status by @benaadams in #6594
  • Fix ParityTraceActionConverter to output init on create by @LukaszRozmej in #6606
  • Fix TraceStore plugin by @LukaszRozmej in #6609
  • Return BlockForRpc from debug_getBadBlocks by @flcl42 in #6612
  • Revise PPA packaging by @rubo in #6618
  • Improve memory management and reduce traffic while serving data to other peers by @benaadams in #6636
  • Add debug_getBadBlocks support by @kjazgar and @Marchhill in #3838
  • Add Metrics.ExposeHost option so a hostname other than "0.0.0.0" can be exposed by @tgerring in #6528

    ⚠️
    For now we decided to keep default behavior so ExposeHost will default to "+" which means "0.0.0.0" but in the future we are going to change default of that flag to "127.0.0.1" to reduce risk of remote access to metrics.

Full Changelog: 1.25.3...1.25.4