You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: