-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incoming peers do not persist. #64
Comments
Troubleshooting with debug level logging revealed that many or most of these connections are coming from peers that are probing the network apparently with no intention of maintaining a persistent connection. So far it looks like nodes with agent strings of: /Ufasoft Coin:0.76/, /bitcoin-seeder:0.01/, and /getaddr.bitnodes.io:0.1/ probe the network every few minutes in this manner. |
As Justus stated above, this is not an issue with legitimate persistent peers, rather it is peers that are connecting to probe the network and then disconnecting. We're going to add the user agent to the "New valid peer" message so it might make it a little more obvious. Currently, the only way to see the user agents of connecting peers is to enable PEER subsystem debugging. |
This commit modifies the new valid peer message to display the useragent. Previously this information was only available by setting the PEER subsystem debuglevel to debug or lower. This was prompted by #64.
Fixes btcsuite#64 and a bunch of broken notification handlers after sending a transaction using sendfrom.
…-txdesc mining: Add json marshal for TxDesc
Outgoing peers appear to be stable, but incoming peers consistently get dropped after about 20 seconds:
The text was updated successfully, but these errors were encountered: