Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BEP-530: Improved Block Producer Selection Mechanism #530

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

buddh0
Copy link
Contributor

@buddh0 buddh0 commented Feb 28, 2025

Description

This BEP proposes a new block backup producer selection mechanism to improve the network stability.
This is the initial version of this BEP, pls refer the BEP directly for the latest content: https://github.com/buddh0/BEPs/blob/improve-block-producer-selection/BEPs/BEP-530.md

@buddh0 buddh0 force-pushed the improve-block-producer-selection branch 2 times, most recently from 5479daa to 872a43b Compare February 28, 2025 07:48
@buddh0 buddh0 changed the title tmp BEP-530: Improved Block Producer Selection Mechanism Feb 28, 2025
@buddh0 buddh0 force-pushed the improve-block-producer-selection branch from 872a43b to 246815b Compare February 28, 2025 09:42
@buddh0 buddh0 marked this pull request as ready for review February 28, 2025 09:51
@buddh0 buddh0 force-pushed the improve-block-producer-selection branch from 0420953 to e03bfea Compare March 3, 2025 02:05
@buddh0 buddh0 force-pushed the improve-block-producer-selection branch from e03bfea to 3c397b1 Compare March 3, 2025 03:07
for order := 0; order < len(validators); order++ {
log.Debug("block producing", "order", order,
"validator index", (inturnIndex+len(validators)-order)%len(validators))
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it is not clear enough

The logic for selecting the in-turn validator remains unchanged, but the logic for selecting backup validators has been simplified. Particularly when Fast Finality is functioning properly, the sequence of block producers can be roughly viewed as validators being selected in reverse order from the `inturnIndex`.

## 5. Backwards Compatibility
A hard fork is required to implement this mechanism.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Backwards Compatibility is to show the impact to ecosystem.
I think validators will be impacted, as the block producer selection mechanism will be changed, it tries to randomize the block producer. Validator collusion can be mitigated, the opportunity to produce block would be faire in long term.

@buddh0 buddh0 marked this pull request as draft March 3, 2025 08:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants