BNB Chain Developers Achieve 88 Percent BSC Testnet Throughput Boost Via BEP-675
On August 7, 2026, BNB Chain developers published BSC testnet benchmark results showing an 88% throughput increase under BEP-675 testing. Network performance reached 2,324 transactions per second on the QANet test environment, up from 1,237 transactions per second during baseline evaluations.
The efficiency gain resulted from streamlining block production without altering existing network parameters. Testing maintained the standard 450-millisecond block interval alongside a 100M gas limit. Unchanged consensus timing confirmed that the capacity expansion stemmed entirely from modified transaction handling.
Under the legacy SendBid mechanism, block builders executed transactions prior to submitting bids to validators. The receiving validators then re-executed every transaction before signing the block. This duplicated process consumed critical processing time during every 450-millisecond slot.
Technical Mechanics of Duplicate Execution Removal
BEP-675 modifies block submission by introducing the SendBidBlock structure. Builders transmit fully executed blocks directly to validators, allowing validators to check consensus rules, sign, and broadcast before running post-signing verification. This structural shift removes 90 to 100 milliseconds of redundant processing.
Removing duplicate execution reduced the validator reserve on the critical path from 125 milliseconds to 15 milliseconds. Block builders gained substantial time to pack additional transactions into each block, resulting in higher average gas utilization without increasing block propagation delays.
Earlier infrastructure efforts addressed network latency, as seen with BNB Chain BEP-590 implementation targeting sub-second block finality. While BEP-590 focused on finality speed, BEP-675 specifically addresses execution efficiency within individual block production windows to maximize throughput capacity.
Benchmark Metrics and Testnet Configuration
The benchmarking took place on QANet, an internal test network structured to mirror the cross-region validator topology of BNB Smart Chain. Both legacy and BEP-675 test runs processed identical mixed transaction workloads routed through block builders and sentry nodes rather than public mempools.
Under legacy SendBid conditions, average block gas usage reached 46.35M out of the 100M limit, with median block gas usage sitting at 29.49M. Roughly one-quarter of blocks were submitted nearly empty because builder execution windows closed before full transaction blocks could be assembled.
With BEP-675 activated, average block gas used increased to 84.15M out of 100M, while median block gas usage rose to 98.99M. The extra packing time enabled builders to fill blocks close to capacity, driving total throughput higher while maintaining consistent execution stability.
Despite higher block gas usage, the P99 finality lag remained constant at 1 to 2 blocks throughout testing. The benchmark demonstrated that processing higher transaction density per slot did not introduce consensus degradation or lengthen finality times across cross-region validator nodes.
Node Requirements and Operational Roadmap
Implementing BEP-675 requires structural updates for network participants. Block builders adopting the SendBidBlock flow must operate a full node rather than a fast node to handle full block execution locally before submission.
Legacy bid submissions remain supported on the network, though legacy builders face shorter transaction assembly windows compared to those utilizing BEP-675. Validators can support the new architecture through client upgrades and standard configuration adjustments.
This scaling effort aligns with broader ecosystem expansion, including dev-focused infrastructure like on-chain AI agent tools for decentralized application creators. Higher network capacity ensures complex decentralized applications can execute high-volume operations with minimal congestion.
BEP-675 is scheduled as part of the BNB Chain second-half 2026 technical roadmap. The proposal will deploy alongside Fork-Free Inclusion Committee (FOCIL) and Block-Level Access Lists to improve overall network scaling.
The documented testnet results reflect controlled benchmark conditions on QANet. BNB Chain developers have not published mainnet deployment schedules or confirmed performance metrics under multi-builder production environments. Further testing will evaluate BEP-675 performance alongside additional second-half 2026 core protocol upgrades.
This article is for informational purposes only and does not constitute financial advice.
