Skip to content

Double-check peer status after syncing to initial head. #17

@g-r-a-n-t

Description

@g-r-a-n-t

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions