You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 1, 2021. It is now read-only.
First, Trinity only requests a peer's STATUS once happened at the handshake, so the peer pool never updates the information of the peer's head slot, finalized root, finalized epoch, etc.
Second, the spec says we should start the sync once we learn the STATUS, while it's not the case in the current implementation.
How can it be fixed
We should request the peer's status once for a while to have the updated knowledge of the peer's finalized root and epoch.
We should have a way to trigger sync immediately after the handshake.
The text was updated successfully, but these errors were encountered:
What is wrong?
Per #1399 (comment)
First, Trinity only requests a peer's
STATUS
once happened at the handshake, so the peer pool never updates the information of the peer's head slot, finalized root, finalized epoch, etc.Second, the spec says we should start the sync once we learn the
STATUS
, while it's not the case in the current implementation.How can it be fixed
The text was updated successfully, but these errors were encountered: