Bitcoin Core will be used as a mule for free, unstoppable CP/CSAM by sickos or state actors, in order to attack Bitcoin and prosecute those who knowingly allow it.
This is the attack...
Once op_return is removed, plain JPEG images (not part of multiple fragments inside scripts that need to be pieced together and decoded, but plain JPEG/GIF/MP4) will be sent through your Bitcoin HardCore node version 30+, from one paedophile to others, possibly sold (Knots runners won't touch them, ever). Your Core node will happily pass it along, providing anonymity to the criminals (or state attackers, or Epstein's old clients).
They will pay a well below market rate initially (eventually zero), and never even need to get the transaction mined - key point. The original filter that Satoshi introduced, FEES, will be effectively bypassed...
After some time, these low-fee CP/CSAM txs will be dropped by Bitcoin Core nodes, but if they don't, the sicko(s) can do an RBF of the transaction (or if they have chained them, an RBF of a single low-fee unconfirmed parent), to cancel and invalidate the transaction so they don't have to actually pay for any of the downstream higher fee large transactions.
They will have successfully used your computer to transfer and potentially sell horrible images, without paying (so forget "filters don't work, they'll get on chain anyway"), thanks you being complicit, and thanks to all the Core devs who allowed this in. And those gaslighting against us saying this is wrong.
Then public opinion will turn heavily against Bitcoiners, if it isn't bad enough now. We already know it's going to get worse as most miss out.
@adam3us has pointed out, incorrectly (I'll explain), that this attack can't work, because of some "package relay". Sounds like this is a filter to stop RBFs of a parent if there is a long chain of transactions dependent on it.
A clever idea, but it can't work, Adam. Do you know why? Because your resistance itself is a form of FILTER, and FILTERS DON'T WORK, remember? You can not use an argument against us if that same argument is used to defend yourself.
An attacker can get their cancelling RBF transaction mined by going directly to a miner. Then the scumbags get away with using your Bictoin Core node for CP/CSAM transmission - it's irrelevant whether it gets on a block or not, it doesn't need to, the paying paedophile got his images.
Ironically, filters not working is the very reason we need filters.
There are 3 solutions.
1) Bitcoin Core reverses this STUPID rushed decision, introducing completely unnecessary risk to Bitcoin.
2) We all run Knots, and it becomes the reference client.
3) We move away from Core to Knots, and maybe others will pop up, and there is no reference client, meaning fewer meaningful changes to Bitcoin become likely.
Bitcoin doesn't need changes; it needs general light maintenance, so just maintain it, don't change it!
x.com/adam3us/status…
