simply not true.

your node will then start relaying this CSAM to other nodes after it comes in a block, I don't see the point of a knob that does nothing except delay for 10 minutes.

this is still true even with 99.999% knots usage. people relaying this stuff won't be doing it through knots nodes.

Reply to this note

Please Login to reply.

Discussion

There’s a difference between what ends up on the timechain and what I choose to accept in my mempool.

And with Core v30 lifting OP_RETURN limits to nearly 4 MB (a 50,000× increase) the risk of vast CSAM being permanently embedded becomes a much bigger issue.

what appears in your personal mempool has no impact on what will be accepted in a block.

My node alone won’t. But enough Knots runners and aligned miners (eg. Ocean) can shape what propagates. You choose defeatism. I do not.

i choose economic reality, in what world would every miner adopt this

The reality we already live in, since filters are how Bitcoin already works. Core v30 is what’s attempting to overturn longstanding mempool policy, not us.

You’re economically illiterate, stay in your lane.

Why isn't it there already then? Please don't say that it isalready there because someone chunked something up to look like utxos and spread it out across lots of transactions. If filters don't do anything why don't we already have big long strings of CSAM in the op return field? Don't say its because no one wants to upload it, someone already went through all the trouble of chunking it up to look like normal monetary transactions.

whos to say its not already?

nostr:note1ct4m02qlyr8mtvad7dv9qmd9qeqv2aplxn6tyt85w5wxr68dsd8q0cns0k

As it turns out, I did ask the question "is it already there". What I found was dishonest people conflating methods akin to steganography with simple drag and drop unencrypted file uploads.