🔔 🔔 NEW OP_RETURN 🔔 🔔

“NIXTHEFILTERS” Filtering JPEGs on Bitcoin is like trying to hold water with a tennis racket. It looks principled until someone points out the puddle. Ocean launched with all the moral authority of a spam-fighting crusade, proudly declaring war on inscriptions. Meanwhile, their own block templates were smuggling JPEGs without even noticing. Then came the receipts: BenTheCarman: https://mempool.space/tx/32806ffe7040f2b57b4f0298f1e3a23d6a3296d25c75afdee5281729f15e8319 Rob Hamilton: https://mempool.space/tx/38086f6079c9eeb1e1a637600645e99982281f5f8ee23dd9680d879b9e7da204 https://x.com/benthecarman/status/1819156196131045496 These weren’t accidents. These were intentional filter bypasses. One of them confirmed in 2 minutes. No tricks. Just miners doing what Bitcoin miners do. Including valid transactions. In February 2024, Marathon released Slipstream. It didn’t just help push complex transactions. It proved filtering doesn’t work. You can’t stop inscriptions. You can only stop yourself from mining them. So what did we learn? Attempts to filter JPEGs, art, privacy, or any other flavor of ‘unwanted’ transaction on Bitcoin are: Economically irrational, technically trivial to route around and guaranteed to fail. http://fixthefilters.com/

https://mempool.space/tx/2154a77befea7b7c1700f37fafa2a3db238b62b891a66df953f08385f3cd178e

Reply to this note

Please Login to reply.

Discussion

Also inscriptions went to zero, because they too were destined to fail.

Once again the right stratedgy was “stack and do nothing”

It would be useful if we could get the raw transaction hex from the website instead of just the txid ✅

That’s the wrong tx 2154a77befea7b7c1700f37fafa2a3db238b62b891a66df953f08385f3cd178e

Just showing you how to get the one you want

The tx was non standard therefore not present in most mempool. So querying that API just does not work until the tx is confirmed on-chain.