pull down to refresh
There are fixed seeds that generally will help, but in case that fails, you can just call addnode <peer ip/onion/etc> onetry over rpc.
But I think Melvin Carvalho's comment was about the fixed seeds, he was pointing out that Todd is one of the fixed seeds and so if a person runs a clearnent node, the software will default to connecting to the fixed node seeds, one of which is Todd's. Did I misunderstand?
Hmm I think he was talking about Peter's DNS seed, which you disable with dnsseed=0. But you don't connect to all seeds iirc (unless that changed and I missed it (which would be bad)).
From the 1000 or so hardcoded nodes in fixed seeds, your node picks a couple (randomly) until you have a sizable address book of peers of your own, then doesn't use them anymore.
You can turn that off too with fixedseeds=0.
This is one of the things I find most frustrating with the current Knots v Core conversation:
source
Yes, fresh node instances query a hard-coded list of peers to get bootstrapped. But I don't know of any node instance that has a brilliant fix for this solution.
Same goes for writing perfect software. Currently, Core has more review than any other project. If other projects receive the same level of review, I anticipate they will find similar levels of bugs.
But instead of talking about the actual issue at hand, dipshits make it seem like these are issues that don't affect us all.
To be fair, there was plenty of dunking on BIP-110 when a few bugs were found in its implementation.