pull down to refresh
Some Bitcoin node implementations such as Libre Relay have less strict mempool policies and relay transactions that would be considered non-standard by Bitcoin Core. Some mining pools use similar mempool policies and additionally accept direct submissions out-of-band.
As transactions with multiple OP_RETURN outputs or larger OP_RETURN outputs are permitted by the consensus rules, blocks that include these non-standard transactions are accepted by all nodes.
Also important to mention: Libre Relay automatically peers with other Libre Relay nodes. So even with only a small minority of Libre Relay nodes, transactions still propagate reliably.
So in other words... attempts to 'filter' transactions successfully by running a client with 'stricter' mempool policy than core... is pretty much hopeless?
????
You learned that today? Sheesh.
My first full-rbf fork of Bitcoin Core with preferential peering was released in 2014.
Censorship, stifling information, is always more difficult than spreading it.
How would someone get around the standardness policy currently for OP_RETURN size?