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
We currently have limited control over the peers that are used for each protocol.
Every time a new request is sent, getPeers() is called, which fetches a new list of peers based on the current nodes that are connected.
This poses as a blocker to retrieve, and control, nodes and perform operations such as renewals.
Proposed Solutions
Maintain a list of nodes that are to be used for each protocol. This should allow to perform operations on these nodes such as disconnection management and renewals.
The text was updated successfully, but these errors were encountered:
This is a feature request
Problem
We currently have limited control over the peers that are used for each protocol.
Every time a new request is sent,
getPeers()
is called, which fetches a new list of peers based on the current nodes that are connected.This poses as a blocker to retrieve, and control, nodes and perform operations such as renewals.
Proposed Solutions
Maintain a list of nodes that are to be used for each protocol. This should allow to perform operations on these nodes such as disconnection management and renewals.
The text was updated successfully, but these errors were encountered: