Flashbots transactions sent through Protect normally cannot be front-run or sandwiched: this article explains how an RPC change can expose a pending swap and how to keep it private.
Public swaps are visible to bots while pending. Front-running means placing a transaction ahead of one the bot has seen. A sandwich attack places trades before and after your swap to profit from the price change. A wallet can show “pending” for either a public or private transaction; that label says nothing about privacy.
Flashbots Protect sends signed transactions to participating builders, which assemble blocks, rather than to the public mempool. The flashbots.app site adds context on the organization’s Ethereum MEV research and the infrastructure behind this routing. Protect’s quick start explains that private routing hides pending trades from public front-running and sandwich bots.
What Can Expose a Protected Swap?
A protected swap becomes exposed when the same signed transaction reaches a public RPC before confirmation. The route decides whether a public bot can inspect the trade.
- Protect route: participating builders receive the private transaction.
- Public RPC: the transaction can enter the public mempool.
- MEV-Share backrun: a searcher’s trade follows yours in the block.
A private swap can become exposed later. Say you send it through Protect, then change your wallet’s RPC while it is still pending. Some wallets may rebroadcast that signed transaction through the new RPC. If that route publishes to the public mempool, bots can see your swap and place trades ahead of it. The original private submission cannot remove a public copy. Protect’s quick start warns that switching RPCs before confirmation can cause a wallet to resend publicly.
The same leak occurs if you submit the identical signed transaction through another public RPC, or your wallet automatically retries it there. Its signature fixes its contents; sending it twice does not create a separate protected swap. Keep it on the private route until it confirms, and know whether your wallet rebroadcasts pending transactions when its RPC changes. Participating builders can see the private transaction, so protection also depends on their handling of it.
MEV-Share may share limited information with searchers to arrange a backrun, a trade placed after your swap. Its introduction says its node currently accepts backruns only. Because that trade follows yours, it cannot move the price before your swap executes or worsen your execution price. It may profit from a price change your swap already caused.
Protect keeps a swap away from public front-running bots while the transaction remains private. Keeping the same signed transaction off public RPCs preserves the reason that protection works.