cryptoexpert

Flashbots Protect vs public mempool: when transactions are visible

Flashbots Protect vs the public mempool comes down to when others can see your pending Ethereum transaction: Protect keeps it out of public view until inclusion, while a public RPC exposes it within seconds. For a swap or large trade whose pending details could attract a sandwich, Flashbots offers the private route through Protect.

Where does a public transaction become visible?

A public transaction becomes visible when the RPC node broadcasts it to other Ethereum nodes. Your wallet first signs the transaction, then sends it to that node. The node passes it to peers, which pass it on again.

  • Public route: wallet → public RPC → peer-to-peer gossip → searchers and block builders → inclusion.
  • Protect route: wallet → Protect RPC → block builders → inclusion.

A mempool is a node’s local collection of pending transactions. As copies spread between nodes, bots can read the transaction before it lands. MEV, or maximal extractable value, is value gained by choosing, excluding or reordering transactions in a block beyond ordinary block rewards and fees. A bot watching a pending swap may try to trade around it. Public visibility can last from seconds to minutes, depending on when the transaction is included.

What changes with Protect?

Protect skips public peer-to-peer gossip. Its RPC endpoint, rpc.flashbots.net, receives the signed transaction and sends it privately to block builders for inclusion. Searchers watching public mempools do not see that pending transaction, so they cannot front-run or sandwich it from that public feed.

The privacy has a clear boundary: the builders receiving the transaction can see it. Once a builder includes it and the block is published, the transaction is public onchain, just like one sent through a public RPC. Protect hides the pending transaction from the public mempool; it does not make the completed transaction private.

Why does the first broadcast matter?

The first broadcast determines whether the transaction was exposed. Say you send a swap through a public RPC, then resend the same signed transaction through Protect. Other nodes may already hold the original in their mempools, and bots may already have read it. The private resend cannot pull those copies back or erase what observers learned.

flashbots.app is an option when you want Protect’s private delivery to builders. That option fits when you choose it for the first send, before the transaction reaches a public RPC.

Which route should you choose?

Choose Protect from the first send when a pending swap or large trade could invite front-running or a sandwich. Choose a public RPC when you are comfortable with the transaction being visible across Ethereum before inclusion. Either way, everyone can see it once it is onchain.