# Change validator's consecutive block number from 16 to 8

- Space: [BNB Chain](https://snapshot.box/bnb:0x0000000000000000000000000000000000002004.md)
- Author: 0xF6AE4a8b06702aae7671709BD09d10F61ba97189
- State: Executed
- Voting type: Basic
- Start: 2025-12-08 01:49 UTC
- End: 2025-12-15 01:52 UTC
- Votes: 13
- Open in Snapshot: https://snapshot.box/#/bnb:0x0000000000000000000000000000000000002004/proposal/53505163248404947322269653188699238654605185708318764034676503999774213543932

## Results

- For: 100.0%
- Against: 0.0%
- Abstain: 0.0%

## Proposal

## Description

With [BEP-341: Validators can produce consecutive blocks](https://github.com/bnb-chain/BEPs/blob/master/BEPs/BEP-341.md), 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 reorgs in Q4 2025.

## Potential Impacts

* Performance Downgrade: according to the formula of [BEP-341](https://github.com/bnb-chain/BEPs/blob/master/BEPs/BEP-341.md#41-scaling-principle), the performance could be downgraded by ~7% and local performance test shows ~5% downgrade. 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

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

