History in the making

🤢🤢🤢

Not gonna watch that. Did he really fell to this shitcoiner’s disingenuous nonsense?

CTV is probably not gonna happen anytime soon and part of the reason is that pro filters and sandwichheads don’t like each other.

Keep doubling down on that retarded logic. The simple truth is this is not a technical debate.

Replacing Core at this point is a matter of survival. The rest of that statement is as retarded as the person that’s making it.

BTCPay server counts?

WTFhappenedinfeb2023 dot com is a real treasure when it comes to context about the current Spam War. If one day there is a book similar to the Blocksize War, this would probably be the main citation source for it.

So if I’m using Jade/Keystone with Sparrow and not their native apps, then I’m good?

Notice the date 👀

The Core one is. The Knots one I run on Windows, since I feel more comfortable with it. But this wasn’t an option for the BTCpay server, so I went with Core, since it’s easier to setup (more manuals available).

Send the asteroid already

Judging by written testimonials I see everywhere, a lot of people that never ran nodes are running Knots now. The net sales of companies like Start9 also suggest that to be true.

I run Knots on an old laptop. I also run core on another (relatively new, low end laptop) for my BTCPay server. Both machines are with 8 gigs of RAM, and both took around 4-5 days to fully sync. Haven’t tried on a rpi, but a couple of people I’ve talked about trying to do a fresh IBD at 4 gigs told me it took them more than 10 days to finish over a decent internet connection.

You know most of that RAM matters during the IBD, right? Have you tried re-downloading the whole chain from scratch? See how much time will take? I also fail to see how Knots is the problem. Maybe you wish to elaborate.

Completely agree. cc:

I see way too many people on Nostr that are still confused about the Core vs Knots debate. This is a tl;dr for them. If a longer explanation is needed, they should go over the website below. tl;dr: SegWit introduced the witness discount, that ended up making junk data up to 75% cheaper, which opened the door for arbitrary data-carrying transactions to directly compete with monetary transactions for blockspace. In practice, that ended up being an unintended de facto subsidy for spam. Taproot then provided a way for inscriptions to sidestep the old datacarriersize filter, which is why the UTXO set exploded from around 4 GB in 2023 to nearly 12 GB by 2025, putting real strain on low-end node hardware. Meanwhile, the Core devs’ reaction has been pathetic — hand-waving it away for two whole years as “free market dynamics” or saying that fixing the exploit is considered “controversial”. At the same time they did a stealth documentation change to pretend the broken filter is “working as intended”. caught them red handed, but instead of apologising for hiding it, they claimed that changing the documentation is a valid way for fixing bugs. Now they’re doubling down their efforts “to fight spam” they willingly allowed by gutting another spam filter (OP_RETURN) that has worked for 11 years, and helped keep 99.9% of all OP_RETURNs at or under 80 bytes. Larger payloads were possible, but never at the absurd size of 100 KB in a single output. Core v30, due in early October, will raise the default limit to 100 KB (an 1200x increase), which makes it trivial to upload entire malware files or worse straight into the chain. This isn’t hypothetical — when BSV made the same change in 2019, it was immediately hit with child p[]rn. The legal and practical fallout for Bitcoin node operators, especially those on cloud infrastructure, hasn’t even begun to be fully grasped. All these absurd and rushed decisions raise the obvious questions: why push this change through despite massive pushback; who stands to profit from it; and why are the real risks of this happening being ignored or swept under the rug? https://wtfhappenedinfeb2023.com

Merged or NACKed by 5 people. 🙄 Are you software engineers always this dense when it comes to analogies? 5 maintainers = “board of directors”. Not every open source dev with ideas and free time.

Go and touch seaweed.

“Knots nodes don’t matter” “You are not technical enough to understand” “You’re falling for social media campaigns based on lies” “You’re unreasonable” This is how Bitcoin politicians will speak one day from the stand. It’s almost comical seeing it happen that early, and on Nostr of all places.

Ok, but have you tried Rakia?

You’d have to be bonkers not to run Knots at this point.

I guess not too many people have seen the video of , so I’ll just post the article below.

#asknostr

This point is so retarded... They’re blaming the functioning op_return filter for the failures of the broken and exploited datacarrier filter. A bug that could’ve been fixed easily. Instead, Core devs twisted themselves into mental gymnastics to avoid repairing it, going as far as doing a stealth edit to the documentation to make it look like the filter was working as intended. Everything that followed is a fallacy built on either incompetence or, more likely, the deliberate malice of five bad actors. It’s that simple.

Nostr quietly making dinosaurs like Instagram obsolete, and most photographers have no clue.

Even the Core simps admit filters can’t censor txs. Lost all respect for Adam Back.

Those woke core kids are playing with fire and I’m not donating for their legal defence costs. Just pointing this out in advance.

Makes sense. The BSV-tards were the ones that claimed responsibility for the inscriptions attack in 2023. I honestly didn’t know that they removed their OP_RETURN filter in 2019 and as a result their shitcoin chain got flooded with child p*rnography files. If you think the exact same thing won’t happen after Bitcoin Core 30 gets rolled out, you’re out of your fucking mind. did you know this or you came to the same conclusion yourself?