g11tech
g11tech
> LGTM. Will not approve since the code + addr will (indeed) likely get updated. this will not change until after devnet0, lets take this in and then re-PR when...
> This is a good point. Lodestar current logic is if `existing_db_last_state.slot < checkpoint_sync_state.slot`, then use the checkpoint sync state. We should change that to `existing_db_last_state.slot < checkpoint_sync_state.slot - offset`...
> wave I'm fairly certain that missing states/blocks in Checkpointz is due to the slot on the epoch boundary not containing a block (i.e. it directly relates to network participation)....
Debugging into the issue and rethinking on it: I think we are doing the right thing, the state corresponding to block's (fetched using checkpoint root) stateroot might or might not...
@philknows also is this a problem which is coming from using a checkpoint published by checkpointz? I think not if they only publishes those checkpoints whos roots are known to...
As we jointly debugged @philknows the issue is when lodestar is not explicitly provided checkpoint from checkpointz (which only displays perfectly epoch boundary block checkpoints), lodestar fetches `finalized` from the...
I think the minimal discovery functionality should be: If you are connected to one peer, you can discover all peers of it and (then connect to them and discover more),...
> correct, thats the discv5 functionality CL use, wondering if geth also uses same/similar
more tests are to be fixed, reopening
@paulmillr @FrederikBolding should this issue be closed off now?