Skip to main content
MEV protection is a Marketplace add-on you manage from your node’s Add-ons tab. It is available on these networks and node types: 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 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 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:

eth_getTransactionByHash

eth_getTransactionReceipt

eth_getTransactionByBlockHashAndIndex

eth_getTransactionByBlockNumberAndIndex

and so on.

​
What happens if private routing fails

While MEV protection is on, Chainstack sends eth_sendRawTransaction only through the private route to block builders. If the private route fails, the request returns a JSON-RPC error, and Chainstack does not broadcast the transaction to the public mempool. Handle the error by sending the same signed transaction again. A signed transaction can be included in a block only once, so a retry can’t execute it twice. MEV protection applies to the node’s existing HTTPS and WSS endpoints and to every authentication method of the node, both the auth token in the URL and the username and password. The node has no separate protected endpoint. To send transactions through the public mempool, disable MEV protection.

​
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 on by default for a new node. When you deploy a node on Chainstack, MEV protection is already selected under Add-ons on the last step. To deploy without it, click Disable on the MEV protection card. A node you create with the Platform API gets MEV protection installed automatically. 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. The Add-ons tab is the only place that shows this status; no JSON-RPC method or Platform API field reports it. To enable MEV protection on a node that doesn’t have it, 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. 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.
Last modified on October 9, 2026