This would result in a cat and mouse game. It defeats the purpose. If their client want to stay connected to rest of the network, it is their right. Let them do it. We can't release an update every couple of hours to a serious client as Bitcoin Core, whenever S2X client changes their own code.
Most of the Core nodes will be unaffected by the fork, they might lose some connections for a moment, that is all. Core clients are a vast majority, they will easily find new nodes and both clients are likely to have majority of their connections to a Core nodes. S2X are making it harder on themselves and are hardly affecting Core. It would be unreasonable to waste so much on peer review and everything for nothing, so just let it go.
Topic: Suggesting an immediate update to properly ban 2x nodes (Read 369 times)
Suggesting an update that will properly ban 2x nodes, given that they are hiding their nodes now and avoiding disconnecting from them.
Example of spotted node while running 0.15.0.1:
"subver": "/Satoshi:1.14.4(2x)/",
https://github.com/btc1/bitcoin/issues/135
This is a serious attack on bitcoin so we need serious protection. The question is, why does the Core node code use only subversion to detect rather than service bit or both?
Example of spotted node while running 0.15.0.1:
"subver": "/Satoshi:1.14.4(2x)/",
https://github.com/btc1/bitcoin/issues/135
This is a serious attack on bitcoin so we need serious protection. The question is, why does the Core node code use only subversion to detect rather than service bit or both?
Jump to: