In a situation where there is only one peer connected we have a logic which can very quickly mark this peer as low quality one:
|
return SyncResponseHandlingResult.LesserQuality; |
It is problematic especially on testing scenario where we set only 1 selected peer to sync from but can be problematic on small chains as well. Would be really nice to improve that part of code to make sure that maybe first node should update pivot and then recheck this peer once more.
In a situation where there is only one peer connected we have a logic which can very quickly mark this peer as low quality one:
nethermind/src/Nethermind/Nethermind.Synchronization/SnapSync/SnapSyncFeed.cs
Line 172 in d18e4f6
It is problematic especially on testing scenario where we set only 1 selected peer to sync from but can be problematic on small chains as well. Would be really nice to improve that part of code to make sure that maybe first node should update pivot and then recheck this peer once more.