Defeated

Change validator's consecutive block number from 16 to 8


ID 795630...0371

ID 795630...0371

Proposed on: Nov 20th, 2025

Proposed on: Nov 20th, 2025

Votes

Proposal

Description

With BEP-341: Validators can produce consecutive blocks, BSC validators were able to produce blocks consecutively, which was intended to improve the overall performance and stability. The consecutive number(TurnLength) was increased to 16 after Maxwell hard fork to maintain same block produce time window.

Large TurnLength value has a side effect: large reorg if the validator fails to produce block smoothly, which could be caused by various factors: network quality, instance performance... And we did observe a few large reorg in Q3 2025.

Potential Impacts

  • Performance: according to the formula of BEP-341, the performance could be downgraded by ~7%. Considering that the current MEV mechanism only consumes part of validator's mining time window, the actually performance impact could be lower.
  • Ecosystem projects that care about the next in-turn validator will need to update accordingly, such as MEV-Builder.

Parameters To Be Updated

There is only 1 parameters to be updated: ValidatorContract: 0x0000000000000000000000000000000000001000

  • turnLength: from 16 to 8
Votes
Status