BNB Chain boosts validator throughput by 40% with BSC-Reth
📋 Summary
BNB Chain says the latest BSC-Reth configuration increased validator throughput by around 40% in internal tests. The Rust client is expected to be adopted by validators by the end of 2026, improving performance and software diversity on the network.
This Friday (6), BNB Chain shared new results for BSC-Reth, an execution client written in Rust and adapted to the high-load conditions of BNB Smart Chain. According to the team, the configuration based on Reth 2.5.1 recorded approximately 40% higher throughput than the previous version, which used TrieDB.
The improvement comes from internal tests, not independent measurements in production. Even so, the result is significant because the network plans to begin migrating validators to BSC-Reth by the end of 2026. In practice, the project aims to process blocks more efficiently without relying solely on the Geth-based client historically used by BSC.
Why BSC needs a faster client
According to the technical report published by BNB Chain, BSC combines three characteristics that put pressure on node infrastructure: a 6.6 TB snapshot, an observed average of 246.7 transactions per second over a one-hour window, and just 0.45 seconds between blocks. In the comparison presented by the team, Ethereum had a 1.6 TB snapshot, 30.81 transactions per second, and 12-second block times.
This profile reduces the time available to execute transactions, calculate the state root, and persist data before the next block. The first stage of BSC-Reth had already reduced p95 block insertion latency by 34.9% and execution latency by 35.5% compared with BSC-Geth. However, validation was still 23.8% slower, indicating a bottleneck in calculating and preparing the state.
The team then incorporated features from versions 2.2.1 and 2.5.
📋 Summary
BNB Chain says the latest BSC-Reth configuration increased validator throughput by around 40% in internal tests. The Rust client is expected to be adopted by validators by the end of 2026, improving performance and software diversity on the network.
This Friday (6), BNB Chain shared new results for BSC-Reth, an execution client written in Rust and adapted to the high-load conditions of BNB Smart Chain. According to the team, the configuration based on Reth 2.5.1 recorded approximately 40% higher throughput than the previous version, which used TrieDB.
The improvement comes from internal tests, not independent measurements in production. Even so, the result is significant because the network plans to begin migrating validators to BSC-Reth by the end of 2026. In practice, the project aims to process blocks more efficiently without relying solely on the Geth-based client historically used by BSC.
Why BSC needs a faster client
According to the technical report published by BNB Chain, BSC combines three characteristics that put pressure on node infrastructure: a 6.6 TB snapshot, an observed average of 246.7 transactions per second over a one-hour window, and just 0.45 seconds between blocks. In the comparison presented by the team, Ethereum had a 1.6 TB snapshot, 30.81 transactions per second, and 12-second block times.
This profile reduces the time available to execute transactions, calculate the state root, and persist data before the next block. The first stage of BSC-Reth had already reduced p95 block insertion latency by 34.9% and execution latency by 35.5% compared with BSC-Geth. However, validation was still 23.8% slower, indicating a bottleneck in calculating and preparing the state.
The team then incorporated features from versions 2.2.1 and 2.5.