Nostr Web Client

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.

Alan ₿ 4mo ago 💬 1

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.

Reply to this note

Please Login to reply.

Discussion

jb55 4mo ago 💬 1

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

Alan ₿ 4mo ago 💬 1

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

jb55 4mo ago 💬 2

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

Alan ₿ 4mo ago

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.

Tauri 4mo ago

You’re economically illiterate, stay in your lane.