> 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

Reply to this note

Please Login to reply.

Discussion

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.

nostr:nevent1qqs2u28d99g50jn3nwk3zk4r04kl5qhep7avgmrcxjajl9pdfs4gf7spz9mhxue69uhkummnw3ezumrpdejz7q3qqyxlpj2gl6dt2nfvkl4yyrl6pr2hjkycrdh2dr5r42n7ktwn7pdqxpqqqqqqztr2qua