&gt; I think the idea here is that you instead privately give the transaction to only your favoured miner. He will then try to hash it, and if and when he finishes it, he will broadcast the transaction and the solution to the network at the same time.<p>That&#x27;s not really a good description of how this will work.  Each miner maintains a transaction pool of transactions that have been broadcasted across the network.  Think of it as a priority queue.  Transactions are of different sizes and fees, and the miner is trying to maximize their total fee up to the 1 MB block size limit.  These transaction pools are largely the same across all miners, with of course some differences owing to time delays and network propagation issues.<p>So all that would happen in miner tumbling is that the miner maintains its transaction pool as normal, but then additionally adds in the special transaction that it does <i>not</i> rebroadcast.  The end result is you end up mining a block that has almost the same transactions in it as any other miner would, except with that one extra special transaction, and a low priority one being bumped.