Pawan Dhananjay
Pawan Dhananjay
Doing some testing with this PR.
Pending testing with high validator numbers.
By default, the metric is only provided when the vc manages < 64 validators. Provided an additional `enable-high-validator-count-metrics` flag for enabling the attestation duty metrics for > 64 validators. Although,...
@karalabe We shouldn't be loosing peers even if the execution engine is offline. Could you share the debug logs for lighthouse as well? It should be in `$datadir/beacon/logs/beacon.log`
Okay I am able to reproduce the issue locally, will check it out.
Thanks for the report! The issue is that we are trying to sync even when the execution layer is offline which leads to a bunch of peers getting banned. We...
@paulhauner the peer downscoring issue is something specific to sync where we ban all peers in a chain if batch processing of that range of blocks fails multiple times (which...
This guy is finally ready for review now! :tada: I'm using similar approaches for both block lookups and range sync. i.e. pause sync when block verification fails because of execution...
Closing this in favor of #3428
We use both the `eth_chainId` and `net_version` to decide the eth1 chain as the eth2 config defines both https://github.com/ethereum/eth2.0-specs/blob/dev/configs/mainnet/phase0.yaml#L54-L55. Agree that we don't really need the eth1 `networkId` for eth2....