> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chainstack.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MEV protection

> Enable MEV protection on your Chainstack Ethereum and BNB Smart Chain nodes to shield transactions from front-running, sandwich attacks, and other value extraction methods.

MEV protection is a Marketplace [add-on](/docs/add-ons) you manage from your node's **Add-ons** tab. It is available on these networks and node types:

| Network | Node types |
| - | - |
| Ethereum Mainnet | [Global Nodes](/docs/global-elastic-node), [Trader Nodes](/docs/trader-node) |
| BNB Smart Chain Mainnet | Global Nodes, Trader Nodes |

On Global Nodes, MEV protection is available on every plan, including the Developer plan.

On L2 sequencer chains — Arbitrum, Base, Arc, and Robinhood Chain — transactions are not broadcast to a public mempool, so there is no third-party front-running to shield against. Use [Optimized Submission](/docs/optimized-submission) instead.

### How it works

1. You construct and sign your transaction as usual and send it through our endpoint. This is sent as `eth_sendRawTransaction`.
2. Instead of broadcasting to the global mempool, our proxy forwards it to the partner network for direct inclusion consideration by block builders.
3. A builder includes your transaction in a block. Once confirmed, it appears on-chain as normal.

If you have the transaction hash, you can retrieve it from the private pool with the regular [eth\_getTransactionByHash](/reference/ethereum-gettransactionbyhash) but only through the same Chainstack node endpoint you used to submit the transaction.

Once the transaction is in the block, you can retrieve it using all regular methods, of course:

<CardGroup>
  <Card title="eth_getTransactionByHash" icon="angle-right" iconType="solid" horizontal href="/reference/ethereum-gettransactionbyhash" />

  <Card title="eth_getTransactionReceipt" icon="angle-right" iconType="solid" horizontal href="/reference/ethereum-gettransactionreceipt" />

  <Card title="eth_getTransactionByBlockHashAndIndex" icon="angle-right" iconType="solid" horizontal href="/reference/ethereum-gettransactionbyblockhashandindex" />

  <Card title="eth_getTransactionByBlockNumberAndIndex" icon="angle-right" iconType="solid" horizontal href="/reference/ethereum-gettransactionbyblocknumberandindex" />
</CardGroup>

and so on.

### Benefits

* Reduced front-running risk — your transaction isn’t visible in the public mempool, minimizing the chance of adversary trades.
* Reliable delivery — direct builder routes ensure predictable inclusion.

### Managing MEV protection

MEV protection is off on a new node until you enable it. The node's **Add-ons** tab shows whether MEV protection is on: its card shows **Active** with a **Disable** button when it is enabled, and **Enable** when it is not.

To enable MEV protection, open your node on Chainstack, select the **Add-ons** tab, click **Enable** on the **MEV protection** card, and complete the install. See [Install a node add-on](/docs/add-ons#install-a-node-add-on).

To disable MEV protection, click **Disable** on the **MEV protection** card. The add-on is removed immediately, and your transactions route through the public mempool as usual. You can enable it again from the same tab.