ethereum / ethereum/trinity-eth2

Double-check peer status after syncing to initial head.

Open
#17 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
16
Forks
9
PR merge metrics
No merged PRs in 30d

Description

As mentioned in ethereum/trinity#1881, we will need to double-check with peers after having imported all blocks up to the head provided in the initial status exchange.

From the spec: *Note: Under abnormal network condition or after some rounds of BeaconBlocksByRange requests, the client might need to send Status request again to learn if the peer has a higher head. Implementers are free to implement such behavior in their own way.*

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.