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

Trickle in validators #1173

Open
sdbondi opened this issue Oct 16, 2024 · 0 comments
Open

Trickle in validators #1173

sdbondi opened this issue Oct 16, 2024 · 0 comments
Assignees
Milestone

Comments

@sdbondi
Copy link
Member

sdbondi commented Oct 16, 2024

Problem

A large enough number of validators register for an epoch to cause the new validators entering in to exceed the previous BFT majority could cause a disruption in conseusus.

Proposal 1

"Trickle in" previously registered but inactive validators at the start of each epoch.

A validator registers and is added to the back of a queue. At the start of a new epoch, $n$ validators from the front become part of the active set.

Acceptance:

  1. Register e.g. 50 validators, only $n$ become active at each epoch until all 50 are in the active set
  2. $n$ is configurable
  3. Tari swarm should still be able to start a new swarm with any amount of validators - after that, any new validators would be queued as normal. To implement this you could specify a minimum amount of validators before the queuing starts e.g. MIN_VALIDATOR_SET_QUEUING_SIZE=50.
@sdbondi sdbondi converted this from a draft issue Oct 16, 2024
@sdbondi sdbondi added this to the v0.8.0 milestone Oct 16, 2024
@ksrichard ksrichard self-assigned this Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

2 participants