It’s not about the spam. IMHO, Bitcoin Core were too dominant, too close to the code and became corrupted. They went against consensus for no good reason. Next time, while many nodes may not paying attention, they could unilaterally push another code change that would reduce #bitcoin immutability even further. They are too close to the code. They are the biggest risk. While not ideal, I run Knots now.
Login to reply
Replies (5)
I think ideally, we should aim to have several good options, with none having too much node-share. Maybe not more than 20%. Long term project, and first we have to win the current battle.
did you get that knots is just core with an insane man's nonsesnical tweaks added? that's like bragging about using mint instead of ubuntu but dumber


Maybe core wants alternative clients to take the spotlight off of them. They dont want to *take the lead* on filtering. Let the node runners have options. Opening up Op_Return is forcing the issue and now alternative clients will rise; node runners have more options/control.
The anti dev thing is not correct and not helpful. IMHO we should be anti-spam, pro do nothing (=dont panic), pro devs.
I agree that filters *work*. By *work* they increase the cost (time/money) to transact around them. However, the fee market is actually the ultimate neutral uncorruptable filter. It is also relentless: they (VC, spam bros, alt token bros) have to pay, then pay, the pay again forever. If their *use* doesnt provide lasting value to humans, then it will be priced out. If it actually does, meaning it outcompetes bitcoin's hurdle rate, then we are collectively better off.
You hate spam, I hate spam, eventually even the spam enjoyers will bend the knee as they run out of resources to keep up with the cost of transaction finality onchain - and will decide, that they hate spam too.
The fee market has our collective backs - forever.
Your argument appears to be, "core devs are playing 4d chess and are actually altruistic, so let's thwart their 4d chess by not calling out their bullshit."
This is convoluted bullshit. If you believe they're doing that, then shut up about it. Call out the bullshit, like you're supposed to do. Maybe you're right, its possible, but it doesn't matter. Have some self control. Or realize its convoluted bullshit and quit wasting time.
They did not go against consensus. Rough consensus is an open software development process and has nothing to do with the opinions of all of us who are not contributors to the code. Knotts doesn’t even have a consensus process, it’s just the changes Luke wants to make to Core.