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
IIUC peers used for filter and lightpus are currently (for the most part) picked randomly. This is ok for most use cases, but it could be interesting to consider making it possible for devs to provider a "priority list" of nodes they want to use.
The reason for this might be they run a fleet of node that they primarilly want to be used in their application - to provide somewhat reliable quality of service and to not rely on potentially less reliable "random" peers.
This need would probably grow stronger with incentivization as well - devs might want to prioritize own nodes for traffic if the nodes get paid/rewarded.
Notes
The text was updated successfully, but these errors were encountered:
This is a feature request
Problem
IIUC peers used for filter and lightpus are currently (for the most part) picked randomly. This is ok for most use cases, but it could be interesting to consider making it possible for devs to provider a "priority list" of nodes they want to use.
The reason for this might be they run a fleet of node that they primarilly want to be used in their application - to provide somewhat reliable quality of service and to not rely on potentially less reliable "random" peers.
This need would probably grow stronger with incentivization as well - devs might want to prioritize own nodes for traffic if the nodes get paid/rewarded.
Notes
The text was updated successfully, but these errors were encountered: