Flashbots Protect

Does the Flashbots Protect Product protect against sandwich and frontrunning attacks from the Flashbots network?

According to the docs:

At a high level these are some of the major benefits of integrating Flashbots Protect:

Frontrunning protection: transactions will not be seen by hungry sandwich bots in the public mempool.
No failed transactions: transactions will only be included if it doesn't include any reverts, so users don't pay for failed transactions. Note: transactions could be included in uncled blocks, emitted to the mempool, and then included on-chain.
Etherscan integration: users can see the status of their transactions on Etherscan.

But, we also know that Flashbots auction auctions off MEV opportunities.

Is it such that Flashbots protects against the public mempool but not the private Flashbots mempool?

Or is there something else going on that I’m not understanding?

Yes, transactions sent through Flashbots Protect are not seen by bots either in the public mempool or the Flashbots private mempool. So they are protected against both.

No bots can see inside the private Flashbots mempool.

2 Likes

Thanks for the feedback! Very cool, so what’s the incentive for flashbots to run this endpoint, is it a goodwill endpoint?

Why wouldn’t everyone just use Flashbots Protect or a “protect-like” endpoint, and not broadcast transactions to a public mempool?

Flashbots primary focus is to enable a permissionless, transparent, and fair ecosystem for MEV extraction. So there is no incentive for flashbots to run this endpoint.

It’s mostly user preference.

1 Like

Thanks for the context. Would there be a downside to not broadcasting transactions? I guess the downside would be that your tx has a MUCH smaller chance of not being included if you only have it on your own node?