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
Doing a private install for a non-technical customer. I want the electrum client to connect only to a single private (self-hosted) server. As such, there should be a mechanism to send either an empty peer list or a custom peer list. For now, all I really need is empty.
for now I achieved this by hacking coins.py and removing the peers, but hoping to get something better in place upstream as that change will be reverted the next time local install is upgraded.
Also, I will mention that is misleading/confusing when looking at the logs and it says eg:
INFO:PeerManager:accepted new peer 4/14 electrum.vom-stausee.de from coins.py
That seems to indicate that a peer connection was made. But apparently it only means that a local peer entry was created, with no connection attempt. I would suggest re-wording this, and/or adding a log entry that no peer discovery or connections will be made when PEER_DISCOVERY="".
This issue is essentially a +1 for issue #199 that was closed without resolution.
The text was updated successfully, but these errors were encountered:
Doing a private install for a non-technical customer. I want the electrum client to connect only to a single private (self-hosted) server. As such, there should be a mechanism to send either an empty peer list or a custom peer list. For now, all I really need is empty.
for now I achieved this by hacking coins.py and removing the peers, but hoping to get something better in place upstream as that change will be reverted the next time local install is upgraded.
Also, I will mention that is misleading/confusing when looking at the logs and it says eg:
That seems to indicate that a peer connection was made. But apparently it only means that a local peer entry was created, with no connection attempt. I would suggest re-wording this, and/or adding a log entry that no peer discovery or connections will be made when PEER_DISCOVERY="".
This issue is essentially a +1 for issue #199 that was closed without resolution.
The text was updated successfully, but these errors were encountered: