Raw form, like everything. But it’s in more than one transaction. Is that enough obfuscation? Would need a command like bitcoin-cli getblock 00000000000000ecbbff6bafb7efa2f7df05b227d5c73dca8f2635af32a2e949 0 | tail -c+92167 | for ((o=0;o<946;++o)) ; do read -rN420 x ; echo -n ${x::130}${x:132:130}${x:264:130} ; done | xxd -r -p | tail -c+9 | head -c184292 > bitcoin.pdf But anyone telling you how to do it will be documenting their crime for you. Opreturn changes won’t change the fact that a command would be needed to make people aware of the illegal numbers on their nodes. I’m totally in favor of knots existing and letting people set any relay policy they want…because sometimes choice matters in ways that are completely meaningless on a technical level… In some ways, by not slowly raising default settings, core is diversifying implementations and I’m happy about that. If anyone really cares about CP relay and the downsides of having such vastly disparate mempools, they could ref write the mempool to keep metadata about valid but spammy transactions each node decided to drop…this way people still can calculate fees properly without participating in spam / CP relay / download until it’s in a block.