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
When starting a recursiveFindContent request, it first looks up the closest nodes in the local routing table.
Then continiously trying to contact closer nodes.
However, data radius of the nodes also plays a role here. We could prioritize on nodes for which the data radius actually falls in the target range (if we know the data radius of the node). It is however to be seen if this added complexity is worth it in terms of amount of nodes we need to contact on average before we find the content.
The text was updated successfully, but these errors were encountered:
When starting a recursiveFindContent request, it first looks up the closest nodes in the local routing table.
Then continiously trying to contact closer nodes.
However, data radius of the nodes also plays a role here. We could prioritize on nodes for which the data radius actually falls in the target range (if we know the data radius of the node). It is however to be seen if this added complexity is worth it in terms of amount of nodes we need to contact on average before we find the content.
The text was updated successfully, but these errors were encountered: