BEP-675 introduces BidBlock to streamline BNB Smart Chain block production, reducing redundant execution and improving scalability.
BNB Smart Chain (BSC) has implemented BidBlock, a block-production mechanism introduced under BEP-675, to address inefficiencies in the traditional block production process. BidBlock eliminates redundant transaction execution by validators before sealing blocks, creating potential for higher gas limits and improved scalability.
Under the legacy SendBid process, builders and validators both execute transactions before a block is sealed, consuming valuable time within the block interval. BidBlock modifies this workflow by allowing builders to submit blocks with execution results already attached. Validators then seal the block and re-execute transactions after broadcast to verify correctness. This adjustment reduces the number of execution passes from three to two, as modeled in BEP-675.
The new process does not automatically raise the network's gas limit but provides builders with more time to construct blocks, enabling higher gas limits if configured. Validators maintain the option to revoke a builder's SendBidBlock permissions in cases of invalid submissions, with fallback to the legacy SendBid process.
Validators verify deterministic header fields against the parent block and consensus rules before sealing. After broadcast, they re-execute the block locally to confirm the submitted results. Normal block validity rules remain unchanged, ensuring network integrity.
The reth-bsc v0.1.3 release supports BidBlock by improving transport and reliability. It uses RLP-encoded binary payloads over gRPC, reducing serialization overhead compared to JSON parsing. Additional features include:
Validators can also use evidence from peers to revoke local SendBidBlock permissions, enhancing the protocol's robustness.
Source link
