> ## 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 nodes to shield transactions from front-running, sandwich attacks, and other value extraction methods.

This currently applies to:

* Ethereum mainnet
* BNB Smart Chain mainnet

### 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.

### Opting out

If you prefer the traditional public mempool route, you can disable private routing. Just switch **MEV protection** to off on the node details page.