Marvelous! There is a validator life cycle, For example, see: https://beaconscan.com/validators, there are pending, active, and exited validators. As the time of writing, the active validator is 507617. Do we count the supermajority (voting threshold) to be 507617 \times 2/3 = 338412? Thanks!
Yeah, they'd lose the 16 ETH on the bug-free chain and be ejected by then. I don't think they would lose their entire staked balance since it is not a slashing event (just a penalty).
And yeah, they'd have to re-stake 32 ETH. Another note that I removed in the article before posting, it isn't feasible to exit during an inactivity leak (with the hopes to re-join later when it all settles down) as only 7 exits can be processed per epoch. So a Validator is forced to stay in the game and pick a blockchain fork.
Marvelous! There is a validator life cycle, For example, see: https://beaconscan.com/validators, there are pending, active, and exited validators. As the time of writing, the active validator is 507617. Do we count the supermajority (voting threshold) to be 507617 \times 2/3 = 338412? Thanks!
Yeah exactly. It is 2/3 of the active validators, so about ~~338,412 for the supermajority.
Yeah, they'd lose the 16 ETH on the bug-free chain and be ejected by then. I don't think they would lose their entire staked balance since it is not a slashing event (just a penalty).
And yeah, they'd have to re-stake 32 ETH. Another note that I removed in the article before posting, it isn't feasible to exit during an inactivity leak (with the hopes to re-join later when it all settles down) as only 7 exits can be processed per epoch. So a Validator is forced to stay in the game and pick a blockchain fork.