Bitcoin Core devs claimed Knots operators were inflating statistics \ stacker news ~bitcoin

pull down to refresh

Bitcoin Core devs claimed Knots operators were inflating statistics protos.com/bitcoin-core-devs-claimed-knots-operators-were-inflating-statistics/

78 sats \ 9 comments \ @0xbitcoiner 9h bitcoin

Bitcoin Core devs falsely claimed this week that almost 40% of Knots nodes — Core’s biggest competitor — had been double counted, giving a false impression of its actual size.

Citing a technical critique of the number of reachable nodes running Knots, they alleged (before deleting many of their posts) that as much as 39% of nodes — 1,758 of 4,468 — were double-counted due to an alleged “sybil attack designed to inflate the number of Knots users.”

For context, the two most popular versions of software for Bitcoin node operators are Core with approximately 80-88% dominance, followed by Knots at approximately 12-19% dominance.

The exact percentage depends on the estimation methodology.

...read more at protos.com

view all related items

82 sats \ 1 reply \ @freetx 8h

Speaking as a non-developer (so I'm sure there are lots of nuance I'm missing).

In a certain sense, this entire debate seems like "bikeshedding" to me. Its kinda like Bitcoin has been going along rather placidly for the last few years without any real pressing development needs. The features being added to core have mainly been bug fixes and small quality of life improvements....

Well, Surgeons like to cut. Lawyers like to sue. Coders like to code. Hence we are now subject to an intense debate that none of the regular users really care too much about. Both sides seem to make decent points on different parts of the debate, but its nearly impossible to discern if either of the arguments actually present a "crises" or not.

Throughout the debate lots of times I find myself sort of agreeing with the last point I read....and I can't really determine: (a) Is there really a problem, (b) Do either of the proposals fix the problem in a demonstrably better way than the other (c) Are the suggested changes representative of a more sinister plot / or is this just bored developers wanting to code?