i'm just pointing out that putting CP on chain doesn't mean everyone who runs it will store CP on their disk. this kind of spam would especially be easy to prune, you could literally just omit all of the spammy transactions from what you store, txs only no data. so, as an attack on bitcoin it would fail to stop people from using bitcoin, because there would be archival nodes elsewhere. and ultimately, the chain is just the headers, the transaction payloads are referred to but you could just prune out the garbage and leave a marker with the tx hash only for calculating the merkle tree. so it could even be basically not stored by anyone at all when CSAM shit is found in data on chain. i agree about the stupid op_return policy shit of core. will, the dev of damus even said some typical bullshit "it's removing a stupid feature, less code to maintain" lol whatever. they aren't going to change the policy API and if they do it's like one of the simplest policy code in the whole thing. it would probably be like 20 lines of fucking code. saying that is a valid reason to remove configuration options for users is fucking bullshit. this is not the bitcoin mindset. deprecation is one thing but just straight removing API elements is completely against the software engineering philosophy of bitcoin (like, you still can use the original P2PKH pre-segwit transactions, removing that function from the wallet would actually make sense compared to removing OP_RETURN policy. lol. i mean, seriously, what the actual fuck.