This PR linked solves the problem for every encoding attackers can invent unlike the treadmill of chasing new filters. It also works in a safe way for you, because all data is deniable always.

A attacker can invent a new way around the filters and post CP as the first TX using that method. No way to defend it because the only way to close every hole is to stop accepting new transactions at all. Because of that filters cannot and will not ever protect you from CP being stored in your chain state.

Step back and remember, the proposed filtering is authoritarian control over bitcoin transactions. Think of the children + we must do something, this is something, we must do this. Classic government marketing for new authoritarian bullshit.

https://github.com/bitcoin/bitcoin/pull/28052

Reply to this note

Please Login to reply.

Discussion

I am aware of that PR, as of yet that is not in the build and is a theoretical fix to that on a deniability basis. Again though, bitcoin is a monetary network and the claim that the thing hindering a robust layer 2 is the size of the OP_RETURN field, is dubious at best. By my estimation therea not a single need for the datacarrier size to be over 100 bytea even in the most complex layer 2s I've seen.

Now minting a shitcoin on bitcoin however takes much more data. I am less concerned with the "Think of the children" wrapping paper than the "Limiting arbitrary data is authoritarian" wrap. It is smuggling so many intended consequences I haven't even thought of the unintended ones.

This just seems like a better argument. Massive respect for both of y'all.