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 @Luke Dashjr and Mechanic @Bitcoin Mechanic

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

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 🚩

'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

OP_RETURN bloat is not necessary Bitcoin is just fine without it So I will keep campaigning I like lots of node runners I work to increase their number

Would somebody please contact Dennis Porter... And have him come on Nostr Unfortunately he is another one of those who do not understand just how much censorship is going on on 'X' and how we need free communication to move Bitcoin along. Nostr rules