// inside head tag

Nethermind v1.33.0: Smaller, Faster and Real-Time UI

Ethereum

September 2, 2025

Intro

Ethereum nodes are powerful but not always easy to run. That changes with Nethermind 1.33.0.

This release introduces the first Nethermind UI, giving operators visibility and control without needing custom dashboards or risky RPC setups. Alongside the UI, v1.33.0 adds experimental history pruning, major performance gains across EVM execution and RPC, and stronger OP Stack support, all focused on making node operations more stable and efficient at scale.

TL;DR

  • Nethermind UI (initial): integrated node interface with safe exposure guidance
  • Historical data live pruning (experimental): keep disk growth in check
  • OP Stack: better peering, finalized/safe handling, optimism RPC namespace
  • Performance: faster EVM paths, leaner RPC, RocksDB v10 and tuning
  • Protocol: new EIPs implemented and devnet updates

Nethermind UI (initial)

This release makes Nethermind easier to operate with the debut of the Nethermind UI: an integrated interface to interact with and monitor your node.

With the UI enabled, you can see block activity, sync status, logs, and mempool flows in real time.

Enable UI health endpoints:

--HealthChecks.Enabled true --HealthChecks.UIEnabled true

Expose UI without exposing public RPC:

--JsonRpc.AdditionalRpcUrls "[http://10.4.0.4:80|http|health,http://localhost:8551|http;ws|net;eth;subscribe;engine;web3;client]"

This example exposes only http|health on the external IP and keeps RPC capabilities bound to localhost.

The Nethermind UI is available today in its initial release. We encourage operators to explore it and share feedback as we continue improving it.

Why this UI matters

Running an Ethereum client has always been powerful, but not always easy. Operators have long asked for a simpler way to see what their node is doing without relying only on CLI logs or setting up third-party stacks like Grafana and Prometheus.

In the Ethereum Client Ecosystem Survey, node operators highlighted their top requests:

  • A native web UI instead of CLI-only workflows
  • Real-time stats and metrics at a glance
  • Better visibility into sync progress and errors
  • Browser-based access from any device
  • Simpler in-built monitoring tools

This release makes Nethermind not only robust in performance, but also one of the most accessible Ethereum clients to operate.

With Nethermind 1.33.0, those requests are now built in.

The new Nethermind UI gives operators:

  • Clear visibility into blocks, transactions, and mempool flows
  • Unified logs and performance metrics in one dashboard
  • Browser-based access on any device with no extra setup
  • Simpler monitoring that reduces operational overhead

From Feedback to Features

Ethereum node operators asked for easier visibility and monitoring. With v1.33.0, Nethermind delivers.

The items above summarize feedback from “Exploring Ethereum’s Client Ecosystem” by Pooja Ranjan (Ethereum Cat Herders, Q1 2023 survey). The survey gathered input from node operators and validators across ~40 countries.

While the sample size was small and not meant to reflect exact network share, the themes were clear: operators want a native web UI, simpler built-in monitoring, clearer sync/error visibility, and lower operational overhead without standing up Grafana/Prometheus. These inputs shaped the first Nethermind UI.

Historical data live pruning (experimental)

Operators now have experimental tools to control disk growth during runtime. This fits our vision of efficient, production-grade infrastructure that adapts as Ethereum scales.

Enable ancient barriers mode:

--History.Pruning=UseAncientBarriers

Enable rolling window mode (~1 year on mainnet):

--History.Pruning=Rolling

By default, rolling mode retains 82125 epochs (~1 year on mainnet). History.RetentionEpochs can be set manually to increase this window, but 82125 is the minimum valid value.

Disable pruning (default):

--History.Pruning=Disabled

OP Stack improvements

In this release, rollup operators benefit from stronger and more resilient infrastructure, including:

  • Safer finalized and safe block handling
  • Smarter peer management for improved stability and faster sync
  • Dedicated optimism RPC namespace

Performance highlights

Operators will see lower CPU and memory usage, faster throughput, and more stable RPC under load. These gains come from a wide set of optimizations across EVM execution, JSON-RPC, networking, and RocksDB.

These changes reinforce Nethermind’s role as the validator client of choice with fastest sync times, proven uptime, and trusted adoption.

Protocol and compatibility

Selected items, with operator impact:

  • EIP-7823 Gas accounting
  • EIP-7825 Transaction gas limit cap
  • EIP-7883 ModExp changes
  • EIP-7907 Contract code size metering
  • EIP-7910 eth_config
  • EIP-7918 Blob base fee updates
  • EIP-7934 Execution block size limit
  • EIP-7939 CLZ instruction
  • EIP-7951 RIP-7212 rename and Osaka enable
  • EIP-7594 PeerDAS support and related updates
  • Plus devnet and chain-specific updates across OP Superchain, Taiko, and Osaka.

Observability and tooling

  • Prometheus support
  • Revamped Hive and Assertoor integration
  • Worldstate benchmarks and HTML or Grafana reporting options

Who should upgrade

  • Rollup and OP Stack teams seeking sturdier peering and sync
  • Validators and node runners who want a UI and better performance
  • Teams preparing for upcoming EIPs and fork timelines

Upgrade and quickstart

Enable UI safely:

--HealthChecks.Enabled true --HealthChecks.UIEnabled true \
--JsonRpc.AdditionalRpcUrls "[http://<external-ip>:80|http|health,http://localhost:8551|http;ws|net;eth;subscribe;engine;web3;client]"

Try rolling pruning (test only):

--History.Pruning=Rolling --History.RetentionEpochs=82125

What’s next

  • UI road map: richer dashboards and actions
  • Pruning graduation criteria and stability work
  • Continued OP Stack improvements and performance engineering

Upgrade to v1.33.0, enable the UI with safe bindings, and pruning remains experimental and not recommended in production. Share your results in GitHub Discussions or Issues, your feedback will help shape the next generation of Nethermind.

Latest articles