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 Jun 11, 2024. It is now read-only.
When doing discovery, the peer should only give us a list of IPs and ports of its peers; it should not include the other fields from P2PPeerInfo.
We will fetch the remaining P2PPeerInfo fields after we connect to the peer and make a status call to it.
Actual behavior
Right now, for peers in our newPeers list, it's possible that the fields could be wrong because a different peer could give us fake values for the fields (they come from third-party peers and not the peer itself).
Currently, we shouldn't trust fields of P2PPeerInfo objects in the newPeers list.
The text was updated successfully, but these errors were encountered:
Expected behavior
When doing discovery, the peer should only give us a list of IPs and ports of its peers; it should not include the other fields from
P2PPeerInfo
.We will fetch the remaining
P2PPeerInfo
fields after we connect to the peer and make astatus
call to it.Actual behavior
Right now, for peers in our newPeers list, it's possible that the fields could be wrong because a different peer could give us fake values for the fields (they come from third-party peers and not the peer itself).
Currently, we shouldn't trust fields of
P2PPeerInfo
objects in thenewPeers
list.The text was updated successfully, but these errors were encountered: