Flashbots: Does Protect fit treasury swaps and records?

If your treasury has heard that Flashbots protects large swaps, its Protect RPC is the relevant service: it keeps transactions out of the public mempool until an Ethereum block includes them. The organization researches and builds infrastructure to reduce harmful maximal extractable value (MEV), including value taken by exploiting transaction order. For a treasury, the practical question is which transactions face that risk and how to record a private submission.

Which treasury transactions benefit from private routing?

Swaps against liquidity pools benefit most because their execution price can change while they wait. A bot that sees a large swap in the public mempool can trade ahead of it, let the treasury’s trade move the pool price, then trade behind it. This “sandwich” can leave the treasury with fewer tokens while still satisfying its approved slippage limit.

A fixed amount ETH or stablecoin payout does not trade against a pool price, so it offers little opportunity for that attack. Private routing is therefore most relevant when an operation exchanges assets through a pool, especially when its size could move the price. It does not make every large transfer cheaper.

What changes in the approval and audit record?

The main change is the evidence available while a transaction is pending. A wallet may show the submitted transaction as pending, but a public explorer will not show its private mempool entry; the transaction becomes visible there when included. An empty explorer search during that interval is neither proof of failure nor proof that funds moved.

That visibility gap gives the approval team a specific decision to make before using the route. Assess whether Flashbots Protect’s pending state fits the record for your next pool swap at flashbots.app, while the signed transaction details are available to approvers. The submission record should identify the approved swap terms, sender, nonce, transaction hash and chosen route, so staff can distinguish “submitted privately” from “completed on-chain.”

Protect omits transactions that would revert, so a failed attempt is not included and does not spend gas. This also means a pending swap may never produce a completion record. Reconcile an unconfirmed attempt as such; if the team replaces it with a different signed transaction, track that transaction’s hash separately.

Once included, the transaction has the same on-chain completion evidence as ordinary routing: its hash, receipt and resulting token movements. Match those to the approved terms rather than treating the wallet’s pending label as settlement. For the next eligible swap, test that your process can record submission, inclusion and an unconfirmed attempt distinctly; that establishes whether private routing fits both approval and reconciliation.

What other conditions affect the choice?

Gas costs and information sharing can change the decision even for an exposed swap.

How much does Protect cost to use?

Flashbots Protect has no separate service fee, but an included transaction still pays Ethereum gas. That amount depends on gas used and network fee conditions; a possible refund is not guaranteed. Compare the expected protection from a sandwich attack with the swap’s execution terms, rather than assuming private routing makes the transaction free.

How does MEV-Share work?

The Flashbots MEV-Share Node can share selected information about a private transaction with searchers, who bid to place a backrun after it. Some resulting MEV may return to the sender as a refund. The information shared depends on the chosen privacy settings, so keeping a swap out of the public mempool does not mean every participant sees nothing before inclusion. That distinction matters if the treasury’s approval also requires confidentiality.