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

feat(validators): trickle validators on Layer 1 #1188

Open
ksrichard opened this issue Oct 25, 2024 · 0 comments
Open

feat(validators): trickle validators on Layer 1 #1188

ksrichard opened this issue Oct 25, 2024 · 0 comments
Assignees
Milestone

Comments

@ksrichard
Copy link
Collaborator

Context

Validators are now controlled by Layer 2, so it decides which validator will be active and when.
This responsibility should be transferred to Layer 1, so we can have proofs that what is the real active validator set (Merkle root hash of them).
Layer 2 should only call Layer 1 through gRPC periodically (or when there is a new epoch) whether what are the currently active validator nodes.

Proposal

Similar logic should be applied on Layer 1 that we have now on Layer 2, so when a new validator node is registered (a new L1 transaction is made), then the new validator node is registered with a different start/end epoch if there are enough validators in the next epoch (so as in L2 just look for the next available epoch).
Meanwhile Layer 2 node can poll Layer 1 (at the start of each epoch) to fetch any new VNs and if there are any, and save them in it's own local DB.

@ksrichard ksrichard converted this from a draft issue Oct 25, 2024
@ksrichard ksrichard self-assigned this Oct 25, 2024
@ksrichard ksrichard added this to the v0.8.0 milestone Oct 25, 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

1 participant