I’m following up on a comment made in response to BitcoinMechanic’s video Fork:
Currently banning peer connections to every knots node that tries to connect to mine.
I saw the logic that was used in the response:
Every connection from a Corev30 node to a non-Corev30 node is one more connection spam does not propagate.
How can one ban pear connections from other Knots nodes? Is it sensible?
It is currently very manual (you have to watch your peers list and kick any Knots nodes off until they are replaced by Core nodes). I am building a patch for Knots (which I’m calling CoreHort) that will preferentially peer with Corev30 nodes, which will be more effective and way less time consuming. I’ll be releasing that in my video after next (next video is part 2 of Garbageman VMM with some big improvements)
Right, so the idea is to actually connect to V30 nodes.
What settings are you guys using now? Im using defaults except I clicked on the checkbox to block tokens too.
I do the same. The Knots defaults are quite sane.
I have
Reject Tokens
Datacarrier cost = 2
Does this mean that those of us that are running Knots on StartOS may actually be excluded from participating in the network going forward?
In the case of Corehort, no. I am writing it to hold two preferential connections to Knots nodes, and the rest to Corev30+ nodes. This ensures we do not kick ourselves off the network, and prevents a type of Honeypot attack that someone like Peter Tod would likely deploy in response.