Skip to main content
Chainstack plans to deprecate Trader Nodes on December 1, 2026. We recommend moving your workloads to Global Nodes before then, as described in Trader Node deprecation.
Optimized submission is a Marketplace add-on you manage from your node’s Add-ons tab. It routes your transactions through a private, optimized path designed to reduce inclusion delays. It applies to L2 sequencer chains, where transactions are not broadcast to a public mempool. It is available on these networks and node types: On Global Nodes, optimized submission is available on every plan, including the Developer plan. On Ethereum and BNB Smart Chain, which have a public mempool where front-running is possible, use MEV protection instead.

How it works

  1. You construct and sign your transaction as usual and send it through your Chainstack endpoint as eth_sendRawTransaction.
  2. Instead of the default node route, it is routed through a private, optimized submission path.
  3. Once included in a block, it appears on-chain as normal, and you can retrieve it with the regular methods such as eth_getTransactionByHash.

What happens if private routing fails

If the optimized submission path fails, Chainstack sends the transaction through the node’s standard route instead, so the transaction still reaches the network. Arbitrum, Base, Arc, and Robinhood Chain don’t broadcast transactions to a public mempool, so the standard route doesn’t expose the transaction to front-running. This fallback differs from MEV protection, which returns an error rather than using the public mempool. Optimized submission applies to the node’s existing HTTPS and WSS endpoints and to every authentication method of the node.

Managing optimized submission

Optimized submission is on by default for a new node. When you deploy a node on Chainstack, optimized submission is already selected under Add-ons on the last step. To deploy without it, click Disable on the Optimized submission card. A node you create with the Platform API gets optimized submission installed automatically. The node’s Add-ons tab shows whether optimized submission 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 optimized submission on a node that doesn’t have it, open your node on Chainstack, select the Add-ons tab, click Enable on the Optimized submission card, and complete the install. See Install a node add-on. To use the standard node route, click Disable on the Optimized submission card. You can enable it again from the same tab.
Last modified on October 16, 2026