Your difficulty is over 1 so you are not submitting 30 partials per minute and hitting the rate limit. OR you have k33 and k34 upping your difficulty.
Some pools adjust difficulty, some do not. It’s the pool operators choice.
1 Like
Anyone on 1.5.1 who is having issues with their farm. Not you specifically as your not getting a rate limit message.
1 Like
well i got these:
full_node full_node_server : WARNING Rate limiting ourselves. message type: respond_peers, peer: 85.243.162.170
full_node full_node_server : WARNING Rate limiting ourselves. message type: respond_peers, peer: 67.84.239.79
there is also no possibility anymore to drop unwanted peer with this version.
1 Like
What makes a peer an “unwanted” one?
1 Like
stucked one with low peak number
1 Like
Looks like you like to have an endless job that leads nowhere.
Sure, chia p2p protocol sucks big at cleanup, and dynamic adjustments (none), but still all that should be done by the p2p protocol, and it is just a waste of time to manually manage those peers.
Also, at some point, someone stated that those nodes are causing harm, if there is a bunch of those. However, that is rather baloney. From syncing point of view, just one node is good enough to sync. An average sync speed is about 0.5 Mbps, so hardly a strain on the other node. So, trying to monitor those peers, knowing that just one node is good enough to sync is a complete waste of time.
2 Likes
they just strain my eyes