Skip to content

Releases: NethermindEth/nethermind

v1.20.0

14 Jul 13:02
@kamilchodola kamilchodola
1.20.0
2d43e90
Compare
Choose a tag to compare
v1.20.0

Release notes

⚠️ This release is replaced with v1.20.1 because of the issue in the eth_getBlockByHash JSON-RPC method which cause problems on Prysm side.

Major highlights

  • Logs readability improvements. Now with color support, improved log organization, and the prominent display of vital information related to block production, it's easier than ever to have a comprehensive understanding of the current head of the chain and all necessary details:

    Break down of new logs:

    Untitled (8)

    • JsonRPC logs are turned off by default.
    • Users of older versions of Windows may need to set registry entry [HKEY_CURRENT_USER\Console\VirtualTerminalLevel] to DWORD 1 to enable colors if using cmd. If colors are too dark they can be adjusted in your terminal color settings.

  • Boosted block processing priority to improve attestation rates during sync

  • Improvements in sync (faster Snap Sync, Old Bodies and Old Receipts) + reduced SSD writes requirement

  • Full Pruning improvements (better threads management, free disk space check for full pruning, pruning time reduced etc).

  • This is the Shapella-ready release for the upcoming hard-fork on Gnosis!
    The Gnosis Shapella hard-fork is scheduled at 11:34:20 AM UTC on August 1, 2023.

Changelog

Gnosis

Cancun

Bug fixes and stability

  • Improve peer discovery and connectivity by @asdacap in #5846
  • Update DotNetty and RocksDB packages (fix issue with installation of Homebrew on MacOS AMD machines) by @rubo in #5883
  • Remove v of non-legacy tx signature from RPC response (#5927) by @rubo in #5927
  • Safety check for full pruning by @deffrian in #5550
    Example usage:
    Now the client will check available disk space to ensure that machine is capable to successfully execute full pruning. To disable this feature set --Pruning.AvailableSpaceCheckEnabled=false
  • Don’t hide precompile contract exception by @asdacap in #5679
  • Fixed pivot-related edge case that could lead to node corruption by @MarekM25 in #5724
  • Copy timestamp from json by @deffrian in #5731
  • Fix stuck state from period offline by @benaadams in #5710
  • Fix point evaluation precompile by @deffrian in #5739
  • Fixed eip2537 activation by @MarekM25 in #5824
  • Quick fix for FullPruner by @marcindsobczak in #5809
  • Bugfix - exchangeCapabilites based on ChainSpec by @MarekM25 in #5801
  • Fix estimate gas by @deffrian in #5800
  • Fix gas fees accounting in TransactionProcessor.Trace by @deffrian in #5743
  • Fix KeccaksIterator not working when some keccak zero prefix is not i… by @asdacap in #5780
  • Fixed fail on precompile dll import error by @Demuirgos in #5725.
  • MaxDegreeOfParallelism defaults for full pruning by @MarekM25 in #5662
    • Introduced few more logs to better navigate through Full pruning process.
    • Revised parameters for --Pruning.FullPruningMaxDegreeOfParallelism parameter
      • -1 - number of logical processors
      • 0 - (DEFAULT) 25% of logical processors. This would reduce overhead of hardware and will give better results of attestations during that process.
      • 1 - In this example, 1 logical processor will be used. Set any value higher than 0
    • Revised parameter --Pruning.FullPruningMemoryBudgetMb and changed the default to 4000 MB

Logging

Performance

  • Boost Block Processor priority to improve attestations during syncing by @benaadams in #5764
  • Apply cache miss hint which improves full pruning perf by @asdacap in #5723
  • Improve db priorities which improves snap sync perf by @asdacap in #5722
  • Apply auto tune to compressed db by @asdacap in #5771
  • Perf/valuekeccak snap code by @asdacap in #5689
  • Optimise Account access and contract detection patterns in Evm by @benaadams in #5646
  • Feature/disable WAL flag which will reduce SSD write requirements during SnapSync phase by @asdacap in #5702
  • Perf/keccak with valuekeccak which results with reduced memory and CPU usage by @asdacap in #5715
  • Perf/faster block load for receipt by @asdacap in #5708
  • Reduce exceptions in Evm by @benaadams in #5727
  • Keccaks: Skip unneeded array allocations by @benaadams in #5735
  • Less contention for OldReceipts and OldBodies by @benaadams in #5737
  • Add option to have multiple network processing thread by @asdacap in #5749
    Example usage:
    In case internet speed is higher than 500Mbps, there is option to set flag --Network.ProcessingThreadCount 32 which may reduce Old Bodies sync phase time
  • Less aggressive peer discovery by @benaadams in #5747
  • Reuse batch Dictionary and skip empty batches by @benaadams in #5802
  • Don't add Keccaks during cache pruning by @benaadams in #5781
  • Optimize Snap sync + Sort DB Batches by @benaadams in #5789
  • Old Bodies sync performance improvement with blobfiles by @asdacap in #5785
  • Add fast test for balance < tx.Value + gas by @benaadams in #5783
  • Remove from ConcurrentDict directly rather than building secondary list by @benaadams in #5779
  • Improve peering management strategy which results with faster sync time by @asdacap in #5772
  • Refactor/Split dispatcher and downloader by @asdacap in #5778
  • Reduce datetime calls in peer discovery by factor of 100 by @benaadams in #5751
  • More efficient EvmPooledMemory by @benaadams in #5752

Other changes

  • refactor state and storage behind one interface by @tanishqjasoria in #5659
  • Address build warnings in Nethermind.Serialization.Ssz.Test.csproj by @MarekM25 in #5695
  • Add support for specifying address in CLI by @emlautarom1 in #5690
  • Move some logic from blocktree into chain level info by @asdacap in #5705
  • Refactor/extract block store from blocktree by @asdacap in #5704
  • One more Engine API test: Blocks_before_pivots_should_not_be_added by @MarekM25 in #5719
  • [README] Add GitPOAP Badge to Display Number of Minted GitPOAPs for Contributors by @kayla-henrie in #4278
  • Revise README by @rubo in #5728
  • Update Nethermind.Crypto.SecP256k1 package by @rubo in #5733
  • Update Nethermind.Crypto.Pairings package by @rubo in #5742
  • Cleanup/remove keccak key by @asdacap in #5748
  • Fix/inconsistently failing tests by @asdacap in #5773
  • Added GnosisSpecProvider and gnosis_loads_properly test by @MarekM25 in #5775
  • Rename BlockChain -> Bl...
Read more

Contributors

rubo, flcl42, and 11 other contributors
Assets 8
Loading

v1.19.3

27 Jun 16:31
@kamilchodola kamilchodola
1.19.3
e8ac1da
Compare
Choose a tag to compare
v1.19.3

Release notes

For the Gnosis network operators, this is a mandatory update because of the upcoming Shapella hard-fork. We urge you to update promptly to ensure seamless network functioning post-fork.

The Gnosis Shapella hard-fork is scheduled at 11:34:20 AM UTC on August 1, 2023.

Changes

  • Add Gnosis Shanghai hard-fork timestamp by @rubo in #5848

Full Changelog: 1.19.2...1.19.3

Contributors

rubo
Assets 8
Loading

v1.20.0-rc

26 Jun 16:42
@kamilchodola kamilchodola
1.20.0-rc
6006747
Compare
Choose a tag to compare
v1.20.0-rc Pre-release
Pre-release

Release notes

Major highlights

  • Logs readability improvements. Now with color support, improved log organization, and the prominent display of vital information related to block production, it's easier than ever to have a comprehensive understanding of the current head of the chain and all necessary details:

    Break down of new logs:

    Untitled (8)

    • JsonRPC logs are turned off by default.
    • Users of older versions of Windows may need to set registry entry [HKEY_CURRENT_USER\Console\VirtualTerminalLevel] to DWORD 1 to enable colors if using cmd. If colors are too dark they can be adjusted in your terminal color settings.

  • Boosted block processing priority to improve attestation rates during sync

  • Improvements in sync (faster Snap Sync, Old Bodies and Old Receipts) + reduced SSD writes requirement

  • Full Pruning improvements (better threads management, free disk space check for full pruning, pruning time reduced etc).

  • This is the Shapella-ready release for the upcoming hard-fork on Gnosis!
    The Gnosis Shapella hard-fork is scheduled at 11:34:20 AM UTC on August 1, 2023.

Changelog

Gnosis

  • Add Gnosis Shanghai hard-fork timestamp by @rubo in #5848

Cancun

Bug fixes and stability

  • Safety check for full pruning by @deffrian in #5550
    Example usage:
    Now the client will check available disk space to ensure that machine is capable to successfully execute full pruning. To disable this feature set --Pruning.AvailableSpaceCheckEnabled=false
  • Don’t hide precompile contract exception by @asdacap in #5679
  • Fixed pivot-related edge case that could lead to node corruption by @MarekM25 in #5724
  • Copy timestamp from json by @deffrian in #5731
  • Fix stuck state from period offline by @benaadams in #5710
  • Fix point evaluation precompile by @deffrian in #5739
  • Fixed eip2537 activation by @MarekM25 in #5824
  • Quick fix for FullPruner by @marcindsobczak in #5809
  • Bugfix - exchangeCapabilites based on ChainSpec by @MarekM25 in #5801
  • Fix estimate gas by @deffrian in #5800
  • Fix gas fees accounting in TransactionProcessor.Trace by @deffrian in #5743
  • Fix KeccaksIterator not working when some keccak zero prefix is not i… by @asdacap in #5780
  • Fixed fail on precompile dll import error by @Demuirgos in #5725.
  • MaxDegreeOfParallelism defaults for full pruning by @MarekM25 in #5662
    • Introduced few more logs to better navigate through Full pruning process.
    • Revised parameters for --Pruning.FullPruningMaxDegreeOfParallelism parameter
      • -1 - number of logical processors
      • 0 - (DEFAULT) 25% of logical processors. This would reduce overhead of hardware and will give better results of attestations during that process.
      • 1 - In this example, 1 logical processor will be used. Set any value higher than 0

Logging

Performance

  • Boost Block Processor priority to improve attestations during syncing by @benaadams in #5764
  • Apply cache miss hint which improves full pruning perf by @asdacap in #5723
  • Improve db priorities which improves snap sync perf by @asdacap in #5722
  • Apply auto tune to compressed db by @asdacap in #5771
  • Perf/valuekeccak snap code by @asdacap in #5689
  • Optimise Account access and contract detection patterns in Evm by @benaadams in #5646
  • Feature/disable WAL flag which will reduce SSD write requirements during SnapSync phase by @asdacap in #5702
  • Perf/keccak with valuekeccak which results with reduced memory and CPU usage by @asdacap in #5715
  • Perf/faster block load for receipt by @asdacap in #5708
  • Reduce exceptions in Evm by @benaadams in #5727
  • Keccaks: Skip unneeded array allocations by @benaadams in #5735
  • Less contention for OldReceipts and OldBodies by @benaadams in #5737
  • Add option to have multiple network processing thread by @asdacap in #5749
    Example usage:
    In case internet speed is higher than 500Mbps, there is option to set flag --Network.ProcessingThreadCount 32 which may reduce Old Bodies sync phase time
  • Less aggressive peer discovery by @benaadams in #5747
  • Reuse batch Dictionary and skip empty batches by @benaadams in #5802
  • Don't add Keccaks during cache pruning by @benaadams in #5781
  • Optimize Snap sync + Sort DB Batches by @benaadams in #5789
  • Old Bodies sync performance improvement with blobfiles by @asdacap in #5785
  • Add fast test for balance < tx.Value + gas by @benaadams in #5783
  • Remove from ConcurrentDict directly rather than building secondary list by @benaadams in #5779
  • Improve peering management strategy which results with faster sync time by @asdacap in #5772
  • Refactor/Split dispatcher and downloader by @asdacap in #5778
  • Reduce datetime calls in peer discovery by factor of 100 by @benaadams in #5751
  • More efficient EvmPooledMemory by @benaadams in #5752

Other changes

New Contributors

**F...

Read more

Contributors

rubo, flcl42, and 11 other contributors
Assets 8
Loading

v1.19.2

09 Jun 20:08
@github-actions github-actions
1.19.2
42ba08b
Compare
Choose a tag to compare
v1.19.2

Release notes

This is an important release for Teku users.

In order to ensure proper functionality with the upcoming Teku release 23.6.0, it is necessary to upgrade Nethermind from version 1.19.x to version 1.19.2. Nethermind 1.19.2 or higher will be compatible with future Teku releases. If you are using a different consensus client or an older Teku version, there is no need to update your node.

This release addresses an issue with engine_exchange capabilities (PR #5787 by @flcl42).

Nethermind versions 1.17 and 1.18 do not require this fix. However, we recommend updating them to the newest version.

Contributors

flcl42
Assets 8
Loading

v1.19.1

07 Jun 08:50
@github-actions github-actions
1.19.1
6fa1393
Compare
Choose a tag to compare
v1.19.1

Release notes

Fixed the regression in v1.19.0 where eth_getLogs requests weren't returning correct results for topics with leading zeroes.
The fix is important for the Rocket Pool community as their integration uses topics with leading zeroes.

Doesn't require resync since the database was not corrupted.

Changelog

  • Fix Keccak iterator not correctly detecting more items when another item is zero prefixed by @asdacap in #5780

Big thanks to @jclapis from Rocket Pool for reporting.

Full changelog: 1.19.0...1.19.1

Contributors

jclapis and asdacap
Assets 8
Loading

v1.19.0

02 Jun 11:57
@github-actions github-actions
1.19.0
19d3be4
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.19.0

Release notes

⚠️ This release is replaced with v1.19.1 because of the issue in the eth_getLogs JSON-RPC method.

Major highlights

  • Significant storage reduction

    ⚠️
    Downgrading from this version to an earlier one is not possible because of the new database format.
    Resync is not required to update to this version. However, you will get the full benefits of disk space optimization only after fresh sync.

  • Faster sync due to the new auto-pivot approach

Details

  • Storage reduction

    v1.18.0 v1.19.0
    Ancient barriers Ancient barriers
    State 166 GB 170 GB 161 GB 161 GB
    Receipts 477 GB 269 GB 152 GB 104 GB
    Blocks 334 GB 222 GB 334 GB 222 GB
    Other ... ... ... ...
    Total 965 GB 678 GB 662 GB 504 GB

  • Receipts DB size reduction

    • Significantly reduced database size by using a different encoding.
      You can’t downgrade from this version without a full db drop and resync. To get the full benefit of the DB size reduction a resync is needed as it will only apply to new receipts. A node will still work fine on 1.19 version without resyncing.
      You can also call the RPC method debug_migrateReceipts(20000000) to rewrite receipts but it only reduces receipt size partially and a resync tends to be faster.
    • Significantly reduced receipt database size by limiting transaction lookup via transaction hash to past year only (similar to Geth). If you need an older lookup, you may keep the old transaction hash index via --Receipts.TxLookupLimit 0.

  • Reduced state DB size by about 5% by not storing commonly occurring patterns.

  • Lowered memory consumption. On the Mainnet, reduces memory usage was reduced by about 1 GB after resync or full pruning.

  • Faster sync due to auto-pivot

    From initialization to snap sync
    v1.17.4 1h 7m 30s
    v1.18.0 28m 22s
    v1.19.0 without auto-pivot 1m 30s
    v1.19.0 with auto-pivot 10s

    State sync will start almost immediately after starting Nethermind. The pivot block will be updated to the one close to the chain head based on the message from the consensus layer. Thus, there’s no need to download a significant amount of the newest blocks before starting state sync.
    By default, auto-pivot functionality in this version will wait for ~15 minutes for CL to send us FCU based on which Pivot will be selected (in the future will be extended). If for any reason FCU will not arrive at Nethermind in that time(no checkpoint sync on the CL side, issue with CL configuration, etc.) you can increase this value by adding the flag --Sync.MaxAttemptsToUpdatePivot=1800 (900 is the default value - 1 attempt = ~1 second, so for 1800 it will try to update the pivot for a total of 30 minutes).

Changelog

Cancun

  • Add JSON-RPC endpoints for EIP-4844, needed to exchange blobs with the consensus layer by @flcl42 in #5558
  • Refactor transaction broadcasting for a needs of EIP-4844 by @marcindsobczak in #5485 #5619
  • Change blob transaction type value to 3 by @flcl42 in #5597

Metrics

Bug fixes and stability

  • Health Checks now will give more useful information about the current syncing status, possible problems during the sync process, and better recognition if a node is healthy by @deffrian in #5630
  • Allow specifying concurrent new connection count and connect timeout by @asdacap in #5676
  • Fix/transactionhash not threadsafe by @asdacap in #5634
  • Use Environment.TickCount64 rather than StopWatch.GetTimestamp by @benaadams in #5575
  • Zero total difficulty in FindBlock by @deffrian in #5581
  • Modernise C# by @benaadams in #5607
  • Set pivot to null if snap and fast sync are disabled by @deffrian in #5454
  • Fix negative blockNumber exception by @deffrian in #5609
  • Shouldn't Wait() on timer threads by @benaadams in #5497
  • Allow specifying local ip. And use any by default instead of loopback. by @asdacap in #5635
  • Add config for eth_getLogs max block depth by @asdacap in #5652
  • Fix eth capabilities for archive nodes by @marcindsobczak in #5655
  • Fix misplaced arguments by @deffrian in #5668

Logging

Performance

Other changes

New Contributors

Full Changelog: 1.18.0...1.19.0-rc

Contributors

rubo, Scooletz, and 9 other contributors
Assets 8
Loading

v1.18.2

26 May 13:32
@rubo rubo
1.18.2
22c0090
Compare
Choose a tag to compare
v1.18.2

Release notes

⚠️
This release revises the timestamp and fork-specific feature activations of the Chiado Shapella hard-fork and is a must-have replacement for any Chiado network operator using the previous v1.18.1.

For the Chiado network operators, this is a high-priority release because of the upcoming Shapella hard-fork. We urge you to update promptly to ensure seamless network functioning post-fork.

For other chains, this is a low-priority update recommended for those syncing from scratch as it significantly accelerates the sync process.

The Chiado Shapella hard-fork is scheduled at 13:17:00 PM UTC on May 24, 2023.

Full changelog: 1.18.0...1.18.2

Assets 8
Loading

v1.18.0

03 May 14:45
@MarekM25 MarekM25
1.18.0
97e80dd
Compare
Choose a tag to compare
v1.18.0

Release notes

Major highlights

  • Significant memory usage reduction
    Check out the graph below for v1.18.0 vs previous versions
    image
  • A new experimental full pruning method
    This significantly reduces full pruning time at the expense of RAM. It can be turned on via --Pruning.FullPruningMemoryBudgetMb <memory budget>. Internal testing shows a 2-4x reduction in pruning time with 4000 MB of memory budget and a 4-7x reduction with 8000 MB with a diminishing return above 16000 MB.
  • Important stability fixes
    We fixed edge case bugs during full pruning that could result in TrieException errors. We also improved the stability of the client by auto repair from the "invalid best state calculation" error. In some setups, Nethermind used to require root permissions because of the current implementation. Issues related to missing total difficulty on archive nodes are also fixed. Check the full changelog for details.
  • Improved sync time and block processing
    In our internal tests with a good network and hardware, Nethermind v1.18.0 can start attesting blocks on the Ethereum Mainnet in just over an hour. After 4 hours, the full download (including bodies and receipts) is completed leading to a steady state and improved attestations.
  • Progress toward the next hard-forks
    We merged @gnosischain withdrawals and started merging 4844-related PRs.

New features

  • Disk space savings for non-validator nodes
    You can significantly save disk space if you don't need chain history -- old bodies and receipts. Validators shouldn't enable this setting, because consensus clients require history to sync deposits. With these settings turned on, you will save around 450 GB of disk space for Ethereum Mainnet. To enable this feature, set --Sync.NonValidatorNode true --Sync.DownloadBodiesInFastSync false --Sync.DownloadReceiptsInFastSync false

  • Configurable startup disk space check
    Added a new check for free disk space during node startup (Health Checks plugin). By default, the node will shut down if available space is less than twice the shutdown threshold or half of the warning threshold (if specified). A new flag --HealthChecks.LowStorageCheckAwaitOnStartup true can suspend initialization until enough free disk is available for safe node operation.

    Change is provided especially to address cases when a node is hosted in an environment with automatic restart, e.g. docker-compose with restart policy.

  • Pass-through RocksDB options
    Allows specifying arbitrary RocksDB settings. The setting must be dynamically configurable. It can be passed as JSON to the --Db.AdditionalRocksDbOptions of DbConfig.

  • Additional metrics output
    A new option of publishing the metrics that can be gathered via dotnet-counters. To enable counters to pass, set --Metrics.CountersEnabled true.
    They can be collected from a running Nethermind process using dotnet-counters collect -n Nethermind.Runner.

Experimental features

  • Flags to tune RocksDB during sync to minimize write amplification at the expense of read amplification (during sync only) saving some SSD write endurance. It can be turned on via --Sync.TuneDbMode <level> where <level> is WriteBias, HeavyWrite, or AggressiveHeavyWrite. Some users may use this to reduce sync time while others may use it to increase it.

Changelist

Cancun

Gnosis

JSON-RPC

  • Added eth_getAccountendpoint by @Demuirgos [#5352]
  • Improve eth_getFilterChanges error codes by @LukaszRozmej [#5513]
  • Added Geth-compatible boolean flags for transaction inclusion for the newPendingTransactionsand newHeads options of eth_subscribe JSON-RPC method [#5299]

Metrics

Bug fixes and stability

Plugin development

To make Nethermind plugin development easier, we published Nethermind reference assemblies as Nethermind.ReferenceAssemblies NuGet package and as a separate archive to GitHub Releases [#5496]

Logging

Performance

Read more

Contributors

rubo, Scooletz, and 19 other contributors
Assets 8
Loading

v1.17.4

20 Apr 14:58
@github-actions github-actions
1.17.4
a576133
Compare
Choose a tag to compare
v1.17.4

Release notes

This is a low-priority release. Bigger changes will come with the release of v1.18.0 that we're currently testing.

This release is intended only for nodes that are syncing from scratch. If a node is already synced with v1.17.3, upgrade is unnecessary.

Changes

  • Updated the sync pivots in the configuration file. Nethermind requires a regular update of sync pivots to get the best sync performance. [#5574]
  • Updated the Sepolia bootnodes to address peering problems [#5567]
Assets 7
Loading

v1.17.3

23 Mar 14:53
@github-actions github-actions
1.17.3
671d60a
Compare
Choose a tag to compare
v1.17.3

Release notes

This is the Shapella-ready release for the upcoming hard fork on Mainnet.
This release is a mandatory upgrade for all users running Mainnet nodes -- all previous versions will stop working on the transition.

No configuration changes are required on the Nethermind side to work properly on the Shapella hard fork.

Please ensure your consensus client is also upgraded to a Shapella-ready version to ensure a smooth transition.
You can check the status of readiness to the Mainnet hard fork of each consensus client here.

The Mainnet Shapella hard fork is scheduled for 10:27:35 PM UTC on April 12, 2023.

Shanghai

Updated the chain spec to Shapella-ready for the Mainnet [#5455]

Assets 7
Loading