It would ba a softfork. We would have the high ground - the others would cause the fork to happen with their anti-decentralization and CSAM ready modification which has no support of Saylor, Mow... Binance etc... People could move later to the chain which is still clean

If enough big names are with us and it becomes obvious that v30 is core's demise, we just fork to prevent any chance CSAM getting on chain. Blocks with OP_Return sizes >~80 bytes are rejected. From Andreas Antonopoulos:

We're nowhere near discussing a 51% attack XMR has to face that risk every day! This is about setting future sails right NO ONE Runs 'core' malware v30

We need a version that physically filters op return blocks out of the chain.

Defend Bitcoin Run A NODE RunKnots

Use Bitcoin for your financial sovereignty? Run A Node Run Knots (It's IMPORTANT)

'X' is a censorship platform My 'reach' there -> 0 Please make people aware that they are never seeing the whole picture Opinions are removed, manipulation is rampant

Satoshi did this (financially) for 'nothing' If 'protocol developers' are being incentivised by fiat hoarders to 'develop' then here is the obvious breakdown of bitcoin to bitcoin corp The users who understand the problem Satoshi solved want bitcoin. Not bitcoin corp

I wish I could be more constructive but at the moment I can only offer thought support

The OP_RETURN war is heating up Seems to me that this could culminate in a fork which nobody wants Lukas - duczko on X wrote: My current understanding of the Core/Knots debate below 👇 Let me know what you think. CURRENT STATE 1. All nodes are blocking the data so <100kb images can’t get stuffed into the chain in easy readable form. 2. Slipstream and MARA wont accept to put illicit images on-chain via their backdoors because it’s a massive business risk for them (and the team would have moral objections too). 3. People that want to put illicit images >80 bytes on-chain are left with the only option to chop up the data in hard to read form. Thereby giving the noderunner plausible deniability and relative safety from government crackdown. 4. As a result the chain is mostly clean from easy readable large 100kb-ish images with illicit content. Yes, there is nasty stuff hidden in convoluted forms, but you have to have special software and know where it is to find it. Thereby, hosting the blockchain is not tied with legal risk. NO FILTER STATE 1. Anyone can put large illicit images >80 bytes into your node. Because you are downloading and decrypting the data in easy readable form by the node software you don’t have plausible deniability and you are exposed to significant personal legal risk. 2. Also, the chain will start getting stuffed with illicit images that everyone will have to store. Which may also become a big problem for node runners down the road, making hosting Bitcoin blockckain into a toxic waste storage operation that many noderunners may opt out of. SUMMARY Core is playing with fire. Changing from current state into a filterless state is not a trivial change as many claim but is connected with significant risk to destroy incentives for noderunners to run nodes. Risking significant decrease in people wanting to run nodes and thereby decreasing Bitcoin decentralization. NOTE An argument I often hear is “only economic node matter”. I’m not sure I agree, but let’s assume it’s true. Then it’s still true that the people running economic nodes have personal risk and if it’s a business then it’s also a team and a business risk that many economic noderunners may not be eager to take.

The time for debate may be drawing to a close. There has to be a way to cure this malware attack. How about knots nodes checking blocks for correctness with the OP_Return data, removing it and storing a new hash for the block with the removed jpeg in the original op_return slot? We need to find a way for Knots node runners to (k)not store CSAM nor forward it. We will have the majority BUT the SPAMMERS WILL GET CSAM into the chain... Thinking caps on time Sent this to Luke and Mechanic

An obvious attack Antifragile mode kicks in So long 'core' The sleeper cell is being put to sleep

The community is waking up. Those who care about bitcoin enough run nodes. Caring means they will notice when an update torpedos the network. Our job is to make sure this deception stays in the spotlight until core lands in the dumpster RunKnots RemoveCoreporation

We got this far by moving We must keep moving If the core is rotten #RunKnots

PLUS Satoshi was NOT a fan of blockchain missuse

Let's remember: Satoshi did this (financially) for 'nothing' If 'protocol developers' are being incentivized by fiat hoarders to 'develop' then here is the obvious breakdown of Bitcoin to bitcoin CORP A centralized corp pushing bitcoin development 🚩