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

Sequential elections #2801

Merged

Conversation

guilhermelawless
Copy link
Contributor

Building off the multi-level election controls added in #2785, this PR changes the block processing behavior to only start an election if the block's ancestors are confirmed.

  • There is a superlinear usage of resources the more elections are active for the same chain, which is now prevented.
  • On confirming an election, the successors (in the same chain and destination chain for sends) are activated (functionality from Sequential voting #2785).
  • Frontier confirmation works as the fallback behavior, for bootstraps and nodes restarting after getting blocks. Backtracking (Bisected election backtracking #2778) later starts the bottom-most election if unable to confirm the frontier.

@guilhermelawless guilhermelawless added quality improvements This item indicates the need for or supplies changes that improve maintainability performance Performance/resource utilization improvement labels Jun 3, 2020
@guilhermelawless guilhermelawless added this to the V21.0 milestone Jun 3, 2020
@guilhermelawless guilhermelawless self-assigned this Jun 3, 2020
Building off the multi-level election controls added in nanocurrency#2785, this PR changes the block processing behavior to only start an election if the block's ancestors are confirmed.

- There is a superlinear usage of resources the more elections are active for the same chain, which is now prevented.
- On confirming an election, the successors (in the same chain and destination chain for sends) are activated (functionality from nanocurrency#2785).
- Frontier confirmation works as the fallback behavior, for bootstraps and nodes restarting after getting blocks. Backtracking (nanocurrency#2778) later starts the bottom-most election if unable to confirm the frontier.
@guilhermelawless guilhermelawless merged commit a6b1129 into nanocurrency:develop Jun 8, 2020
@guilhermelawless guilhermelawless deleted the sequential_elections branch June 8, 2020 12:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
performance Performance/resource utilization improvement quality improvements This item indicates the need for or supplies changes that improve maintainability
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants