F2Pool is actively attacking the network RIGHT NOW. All it takes is one attacker to send them a single instance of CSAM, and Bitcoin users will have to knowingly and intentionally receive, store, and distribute it until the end of time. This will permanently impact Bitcoin adoption regardless of whether governments turn a blind eye or prosecute. If miners are going to switch pools when they do bad things, NOW IS THE TIME.
I don't care if you switch to Foundry or even Antpool. Obviously I would prefer you make your own blocks and use OCEAN, but this is too critical and time-sensitive to be picky. We can work on mining decentralization and spam issues over a longer period of time, but CSAM is an insta-kill we MUST avoid.
Thread
Login to reply
Replies (27)
what actionable steps should one take right now?
Don't mine with F2Pool, and tell everyone you know who does.
easy enough
Done. I'm not sure why anyone would mine anywhere but ocean right now. Less fees and actual configurability.
Thanks for your work @Luke Dashjr
What about brains? We need some easier way to install datum on arm like raspberry pi
Braiins no longer runs a pool, they just proxy to Antpool. But again... anything but F2Pool is an improvement for now.
Lots of people use DATUM on a Raspberry Pi. Though Pi isn't very good at running a node since the last spam wave.
Ah OK I found a way to compile it for arm.
People are always going to do stuff we don't like.
The timechain is something shared by humans, like the oceans. People pee on it and we still bathe in them.
Are they stating they will mine known CSAM?
Any evidence or specifics at all or just hyperbole?
The exact thing happened to BSV in 2019 when they blew open op_return. It’s not a prediction, it’s a history lesson.
Source pls

put it on nostr?
Hauahaua
Reflecting on this situation, the node runners and anti-spam movement are true Bitcoiners, understanding Bitcoin’s monetary nature and aiming to preserve it as a means of exchange, not just data hosting. They are cautious, trying to avoid a fork and maintain chain integrity.
Initially, Bitcoin Core accused people like @Bitcoin Mechanic and the Knots community of causing a fork, but this reveals their own intentions. It seems Core might trigger a hard fork, especially since they’re developing “Libre Relay,” possibly leading to a “LibraCoin,” similar to Facebook’s project. The engineers’ goal of centralization under “coordination” contrasts with node runners who preserve Bitcoin’s original purpose.
If the fork occurs, we’ll sell the LibraCoins into hype and stack sats.
It's obvious Core "Maintainers" don't have a lot of Bitcoin...
I have serious concerns with this framing.
The legal argument doesn’t hold up. Node operators aren’t liable for encrypted data they didn’t create and can’t access. ISPs, CDNs, and Tor nodes have legal precedent here. What makes Bitcoin nodes different?
CSAM has likely already been encoded in the blockchain for years through various methods. If this is truly an insta kill for adoption, why hasn’t it already happened?
If Bitcoin can be killed by one attacker sending one instance of illegal content, then it was never antifragile. This argument concedes Bitcoin can’t survive adversarial use, which undermines the entire value proposition.
And switch pools NOW but obviously I prefer OCEAN? That undercuts this being about Bitcoin’s survival rather than pool market share.
If I’m missing something in the legal or technical analysis, I genuinely want to understand it
View quoted note →
The CSAM argument is a clear example of the slippery slope fallacy.
Why are you always such a phaggot Luke?
F2Pool’s stunt proves centralized mining’s a ticking time bomb for Bitcoin’s freedom.
@Luke Dashjr I’m trying to configure my DATUM and it’s not hashing. Not sure what’s up, I was following the instructions.
I've been running a node for years and I've never seen an image of any kind on the chain.
Closest I've ever seen to the "spam" that chicken little keeps yelling about was the Bitcoin Genesis block, which copied a news article about a bank bailout in the UK happening at the time.
@Luke Dashjr there is a possible solution to this. Let's chat.
