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'd want to be careful to ensure that peers which send us new wire messages we don't yet understand are exempt from this banning. With the addition of BIP 151, peers may attempt to optimistically set up an encrypted session within the active connection before version negotiation. If we ban based on an unknown message (since we haven't implemented this yet), then we'd erroneously be dropping peers within the network that support the new encryption features. FWIW, the only implementation I'm aware of that has implemented BIP 151 is bcoin.
On a related, note it's puzzling as to why BIP 151 didn't include a new service bit, or a bump in p2p protocol version. Either of those signals would avoid the scenario of a peer sending a message to another peer with uncertainty as to if they're able to process/recognize the message.
btcd should ban hosts that do not follow the wire protocol. For developers needing to test, a --whitelist option should be available.
The text was updated successfully, but these errors were encountered: