# Flashbots Protect

**URL:** https://collective.flashbots.net/t/flashbots-protect/507
**Category:** Block Builders
**Tags:** question
**Created:** [October 11, 2022, 1:54pm UTC](https://collective.flashbots.net/t/flashbots-protect/507 "2022-10-11T13:54:53Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![PatrickAlphaC](https://collective.flashbots.net/user_avatar/collective.flashbots.net/patrickalphac/32/456_2.png) [@PatrickAlphaC](https://collective.flashbots.net/u/PatrickAlphaC)
#### Post date: [October 11, 2022, 1:54pm UTC](https://collective.flashbots.net/t/flashbots-protect/507/1 "2022-10-11T13:54:53Z")

</div>

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

[According to the docs](https://docs.flashbots.net/flashbots-protect/overview):

```auto
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](https://docs.flashbots.net/flashbots-auction/overview) 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?

---

<div class="post-metadata">

### Author: ![bert](https://collective.flashbots.net/user_avatar/collective.flashbots.net/bert/32/1850_2.png) [@bert](https://collective.flashbots.net/u/bert)
#### Post date: [October 12, 2022, 12:10pm UTC](https://collective.flashbots.net/t/flashbots-protect/507/2 "2022-10-12T12:10:13Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![PatrickAlphaC](https://collective.flashbots.net/user_avatar/collective.flashbots.net/patrickalphac/32/456_2.png) [@PatrickAlphaC](https://collective.flashbots.net/u/PatrickAlphaC)
#### Post date: [October 12, 2022, 2:08pm UTC](https://collective.flashbots.net/t/flashbots-protect/507/3 "2022-10-12T14:08:31Z")

</div>

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?

---

<div class="post-metadata">

### Author: ![bhaki](https://collective.flashbots.net/user_avatar/collective.flashbots.net/bhaki/32/853_2.png) [@bhaki](https://collective.flashbots.net/u/bhaki)
#### Post date: [October 24, 2022, 8:04am UTC](https://collective.flashbots.net/t/flashbots-protect/507/4 "2022-10-24T08:04:58Z")

</div>

> [@PatrickAlphaC](#):
>
> Thanks for the feedback! Very cool, so what’s the incentive for flashbots to run this endpoint, is it a goodwill endpoint?

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.

> [@PatrickAlphaC](#):
>
> Why wouldn’t everyone just use Flashbots Protect or a “protect-like” endpoint, and not broadcast transactions to a public mempool?

It’s mostly user preference.

---

<div class="post-metadata">

### Author: ![PatrickAlphaC](https://collective.flashbots.net/user_avatar/collective.flashbots.net/patrickalphac/32/456_2.png) [@PatrickAlphaC](https://collective.flashbots.net/u/PatrickAlphaC)
#### Post date: [November 3, 2022, 2:07pm UTC](https://collective.flashbots.net/t/flashbots-protect/507/5 "2022-11-03T14:07:17Z")

</div>

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?

---

<div class="post-metadata">

### Author: ![PatrickAlphaC](https://collective.flashbots.net/user_avatar/collective.flashbots.net/patrickalphac/32/456_2.png) [@PatrickAlphaC](https://collective.flashbots.net/u/PatrickAlphaC)
#### Post date: [July 26, 2023, 9:30pm UTC](https://collective.flashbots.net/t/flashbots-protect/507/6 "2023-07-26T21:30:46Z")

</div>

Just following up here. I still don’t understand.

According to the [flashbots docs](https://docs.flashbots.net/flashbots-protect/overview), it says:

> Flashbots Protect makes it easy for everyday users and developers to use Flashbots for frontrunning protection.

However, it goes on to say:

> We abstract away the complexity of submitting bundles to the Flashbots Auction and make integrating as simple as adding a URL to MetaMask.

This makes me think it’ll protect me from _public_ sandwich and front-running bots, but not _flashbots_ sandwich and front-running bots.

It _then_ goes on to say that all transactions are sent the the [MEV-Share](https://docs.flashbots.net/flashbots-protect/rpc/mev-share) node.

> Flashbots Protect users’ transactions automatically flow to the Flashbots MEV-Share Node, which returns them up to 90% of the MEV that their transactions create.

Which makes me think, “ok, clearly Flashbot protect is _not_ protecting me from MEV… what gives?”

Do I have that correct?

---

<div class="post-metadata">

### Author: ![bert](https://collective.flashbots.net/user_avatar/collective.flashbots.net/bert/32/1850_2.png) [@bert](https://collective.flashbots.net/u/bert)
#### Post date: [July 27, 2023, 8:50pm UTC](https://collective.flashbots.net/t/flashbots-protect/507/7 "2023-07-27T20:50:10Z")

</div>

Well, only selective data is shared by the MEV-Share node. Enough to enable e.g. blind arbitrage, but not enough to enable sandwiching. So users are protected from sandwiching but still can benefit from being backrun.

---

<div class="post-metadata">

### Author: ![Fred](https://collective.flashbots.net/user_avatar/collective.flashbots.net/fred/32/1288_2.png) [@Fred](https://collective.flashbots.net/u/Fred)
#### Post date: [August 28, 2023, 2:25pm UTC](https://collective.flashbots.net/t/flashbots-protect/507/8 "2023-08-28T14:25:49Z")

</div>

Thank you for the feedback @PatrickAlphaC – I just watched your [video](https://www.youtube.com/watch?v=92bdU5uvsD8) and read the [thread](https://twitter.com/PatrickAlphaC/status/1695071101573804537?s=20) you posted regarding Flashbots Protect.

Great tutorial, and very valuable feedback on the Protect docs. We’ll update the [overview page](https://docs.flashbots.net/flashbots-protect/overview) for Protect based on your feedback to clarify that MEV-Share _only allow for backrunning_, The 90% MEV users might receive is from searchers executing transactions _after you_ to clear out arbitrage opportunities.

If you have additional feedback, thoughts, ideas or questions – please let us know, it is very much appreciated!

---

<div class="post-metadata">

### Author: ![PatrickAlphaC](https://collective.flashbots.net/user_avatar/collective.flashbots.net/patrickalphac/32/456_2.png) [@PatrickAlphaC](https://collective.flashbots.net/u/PatrickAlphaC)
#### Post date: [August 31, 2023, 1:41am UTC](https://collective.flashbots.net/t/flashbots-protect/507/9 "2023-08-31T01:41:07Z")

</div>

Of course! Thank you for making this product!

Glad the video was helpful! If you think of other cool ways to bring exposure to this product, let me know!
