Knots people bragging that the most common single version running means they've won win core versions outnumber knots versions.
At least they are consistent in bragging about doing things they haven't done.
Knots people bragging that the most common single version running means they've won win core versions outnumber knots versions.
At least they are consistent in bragging about doing things they haven't done.
I'm really glad Nick Szabo has started speaking up about it. He's got the right idea. The goal shouldn't be to replace core, or even keep the op_return limit - it should be fixing the mistakes that led to this situation in the first place. Like the witness discount.
What are the odds of getting consensus on the consensus rules themselves if all hell breaks loose over a mempool policy?
I'm totally fine letting them believe they've "won" if that means they'll finally stop with the bs rhetoric and rage farming. I'm afraid however they'll try to find their next imaginary enemy as soon as possible 😂
Scorecard:
-0% of thr network running Core 30
-21% of nodes now properly filtering inscriptions and climbing
-Core Devs credibility in the toilet
What metric are using that doesn’t point to this being a disaster of their own making?
Just because core is a mess doesn't mean knots solves shit. I wasn't talking about core. I was talking about how knots is celebrating winning when they haven't won and even if they did win by the standard they originally set it wouldn't solve the problems they are complaining about.
Its important for Knots to be the biggest, then everything else has to conform to the Knots chain, or risk dying.