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
Imagine this situation: the light client starts, connects to a node, and warp syncs to block 500. It then switches to "all forks syncing".
Later, it connects to a node that advertises block 100000.
In that situation, the light client should try to warp sync to block 100000 from that other node while keeping in mind that this other node could be malicious.
Basically, the AllSync state machine should continue running the warp sync state machine even after it's done.
The text was updated successfully, but these errors were encountered:
Imagine this situation: the light client starts, connects to a node, and warp syncs to block 500. It then switches to "all forks syncing".
Later, it connects to a node that advertises block 100000.
In that situation, the light client should try to warp sync to block 100000 from that other node while keeping in mind that this other node could be malicious.
Basically, the
AllSync
state machine should continue running the warp sync state machine even after it's done.The text was updated successfully, but these errors were encountered: