this narrative is not correct. lifting the placebo filter doesn't allow large OP_RETURNs to suddenly start happening. we are not sitting around anxiously waiting for core to push the big evil button, after which it will be possible for the first time. it already happened.

the largest OP_RETURN on bitcoin happened 298 days ago and it was 79,870 bytes, which is over 7 times bigger than your profile picture. it appears to have been submitted to slipstream, meaning someone told it directly to a miner and bypassed the mempool completely. the filter didn't work. it looks like it was a runestone, so it's probably a picture. if you don't have pruning enabled, it's on your computer right now.

https://bitcoin.stackexchange.com/questions/126131/whats-the-largest-size-op-return-payload-ever-created

and you seem totally lost about what citrea even does. its sequencer posts zero knowledge proofs onto bitcoin of transactions that happened on a separate blockchain. it does not post the transactions themselves. this is a GOOD thing if you don't want people doing ethereum-type stuff directly inside the bitcoin blockchain.

Reply to this note

Please Login to reply.

Discussion

I don't think that's true either. I don't agree with your root cause analysis or your bogeyman selection. it became normalized to tell transactions directly to miners when blocks first started being full. this is what opened up the can of worms with nonstandard-but-valid transactions becoming more common than they were before. if you still want to blame core for something, you can blame them for this.

sorry, you're wrong again. mara slipstream is currently in operation and can be accessed here:

https://slipstream.mara.com/

here is an example of a nonstandard transaction that they included recently. it was never in the mempool.

https://mempool.space/tx/22d920c4ef593fb107857be1991e5ee42ec4b2210a53f3721a138732999ec7a8

The haven't stopped their Slipstream.

They have stopped accepting transactions with sub 1 sat per vB fees because of the nodes policies ...

and these node policies deter slipstream from including some types of nonstandardness but not others because?

deter mass abuse

I mean if I ran this kind of thing I'd want extra on top of the going rate just because it's custom and costs extra to operate

𝓘𝓕 𝓨𝓞𝓤 𝓑𝓡𝓔𝓐𝓚 𝓨𝓞𝓤𝓡 𝓛𝓔𝓖𝓢

𝓘𝓣'𝓢 𝓗𝓐𝓡𝓓 𝓣𝓞 𝓒𝓞𝓞𝓚 𝓞𝓡𝓐𝓝𝓖𝓤𝓣𝓐𝓝

This was hilarious