Super Testnet's avatar
Super Testnet 3 months ago
> Not one answer for the fact that I keep posting that knots real solution is that they are making Cloudflare scanning a defacto part of Bitcoin by insisting on a solution that makes all large op_returns MARA and trusting their scanning slipstream submissions The knots solution does not make *any* large op_returns MARA The knots solution simply filters large op_returns from your own mempool If a spammer therefore submits the large op_return to MARA that is not knots' fault, and if MARA mines it, that too is not knots' fault > ocean, datum, and knots are the best way to put CSAM on chain before core 30 How so? I am not familiar with this claim
↑ Parent

Replies (1)

Bill Cypher's avatar
Bill Cypher bill@nostrplebs.com 3 months ago
Slipstream is a path right around knots. Knots has 0 ability to keep CSAM out of the chain. That means what knots is really counting on to keep CSAM off chain is whatever screening method MARA uses for slipstream. The mempool only thing is a dodge to avoid facing the real problem. If it gets on chain by any path every node has to serve that block from that day to the end of bitcoin. Mempool is not a real solution to the real risk. I am the only one I have seen put together this claim. Here it is.
Bill Cypher's avatar Bill Cypher
Pre core 30 thinking the situation before the change through. Miners offering large op_returns scan them for illegal content. Makes sense. If MARA accepts CSAM we can all see that it went into the block they mined and was non standard. Legally very risky for them with a permanent public immutable record that it came from them. Only if others start relaying large op_returns do the large pools offering this service have deniability that maybe the illegal content came from the wider mempool somewhere. That means before core 30 you need to basically run your own anonymous service for your own configurable block templates and then mine a block if you want to put CSAM on chain and maybe get away with it. Follow so far? That means that before core 30 the easiest way to put CSAM on the blockchain is Ocean, DATUM, and Knots combined with a hash rate for hire service. RIP my replies.
View quoted note →
↑