danny
danny
I think the following captures what we'd like to see while being a bit less punitive than @dankrad's original proposal * track `non_finalized_counter` in beacon state. init to 0 *...
Generally agreed. I think this is sensible to get into the proposed "first" fork that might include adjusting punitiveness, light client support, etc. There are a few places of concern...
Looks generally correct to me. Haven't done deep review of the test scenario
This is a known bound chosen and based on the instantiation of the beacon chain on mainnet Ethereum, assuming a maximum suppy of ~130M ETH and thus a maximum number...
I don't think these need to be strictly illegal, and in fact we used to have a type that was set to length `0` because it was essentially "disabled". Using...
I'm not certain that having the flag overrides buys us much time in practice given that (1) clients will cut releases almost certainly anyway (thus we prbably assume the worst...
Curious -- what slot does the p2p reference state sit at?
I agree that a manual override is valuable in event of unexpected events near the merge. Other than a slow down, you could also see a repeated 51% attack/reorg that...
This is a known issue due to (very likely) sparse block proposals during an inactivity leak. The amount penalized is very small but serves no game theoretic purpose and is...
Thanks for the feedback. I'm working on a PR and will ping the participants here for input