// inside head tag
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.
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.
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:
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:
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.
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
In this release, rollup operators benefit from stronger and more resilient infrastructure, including:
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.
Selected items, with operator impact:
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
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.