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

Implement WaitForActivation in Validator Client #1456

Closed
rauljordan opened this issue Feb 1, 2019 · 0 comments · Fixed by #1896 or #1898
Closed

Implement WaitForActivation in Validator Client #1456

rauljordan opened this issue Feb 1, 2019 · 0 comments · Fixed by #1896 or #1898
Labels
Priority: High High priority item
Milestone

Comments

@rauljordan
Copy link
Contributor

We need a way to listen for a validator being activated in the validator client after the chain has started. This only applies for validators which have issued deposits into the deposit contract after ChainStart.

According to the validator specification doc here:

Deposits cannot be processed into the beacon chain until the eth1.0 block in which they were deposited or any of its descendants is added to the beacon chain state.eth1_data. This takes a minimum of ETH1_FOLLOW_DISTANCE eth1.0 blocks (~4 hours) plus ETH1_DATA_VOTING_PERIOD epochs (~1.7 hours). Once the requisite eth1.0 data is added, the deposit will normally be added to a beacon chain block and processed into the state.validator_registry within an epoch or two. The validator is then in a queue to be activated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: High High priority item
Projects
None yet
2 participants