It's not core vs knots.

It's spammers vs Bitcoin

Who benefits by making node running unaffordable? (Allowing spam means node runners have to pay for more storage, it'll also increase cost to run a node because of internet cost)

Who benefits by making node running illegal? (allowing child pornography on the blockchain will make node running illegal)

Why the fuck is this even a debate? Did we not already have this debate and find a solution back on 2014 or 15 or something it was a while ago I barely remember but I know we have already gone over this before

Reply to this note

Please Login to reply.

Discussion

It’s really just running knots the ultimate solution?

Honest question

Its not the ultimate solution. Its only a step in hopefully the right direction. The ultimate solution isn't even the client we use - its decentralization of the mining. Even if 100% of nodes run knots, and all of them filter appropriately, the garbage will still get on chain because they just do what they've been doing, which is going directly to the big mining companies and paying "out of band" (more/not in the same block as the image). This is only possible because big mining companies can be sure they'll get a block. Decentralization is the only true fix - plus filters. If Core 30 happens, even if we decentralize perfectly, we still lose. If Knots wins perfectly, but mining stays centralized, we lose. Its high stakes. We haven't been nearly focused enough on fixing the mining.

Knots becoming the majority of nodes isn't the ideal. There should be a bunch of options. This is just the necessary first step.

Personally, this is what I'm here for. Its easy to be a low effort bitcoiner, but I'm not here for that. I post spiritual shit when I'm bored. But I'm here to fight the right fights so that Bitcoin wins. I'll physically show up when the time is right, too. There's a lot of work to do.

OCEAN & Datum are trying. Another reason why I trust what that team says, though I'm not very technical

Agreed. They've got some hefty proof of work behind them.

I'm not sure either. What I understand is that there is a defect in Taproot that needs to be fixed; filters from Segwit were mistakenly not carried over in to Taproot. Also, 32-40 bytes is all that anyone should need to anchor a hash to the Bitcoin blockchain. Knots filters can help with the latter but not the former