Polygon Private Transactions & MEV Protection

Hyperstrate is an independent private transaction provider for Polygon. Instead of broadcasting your transaction to the public mempool, you send it to the Hyperstrate private RPC, which routes it privately toward block production. Once it’s included in a block, it settles on Polygon like any other transaction.

Polygon private transactions are ordinary signed Polygon transactions that are submitted through a private channel instead of being broadcast to the public mempool. While they wait for block inclusion, bots watching the public mempool can’t see them. After inclusion they’re recorded onchain and are as public as any other transaction. Read what private transactions on Polygon are for the full picture.

A Polygon private RPC is a JSON-RPC endpoint that accepts your signed transactions and forwards them through private infrastructure, rather than gossiping them to the public peer-to-peer network. Your wallet, bot or backend talks to it like any other RPC. With Hyperstrate, you point transaction submission at the Hyperstrate endpoint and authenticate with your API key. Learn how a Polygon private RPC works.

A public RPC endpoint forwards your transaction to the public mempool, where node operators and bots can see it before it’s included. A private RPC endpoint forwards it through a private path toward block production instead. A dedicated or paid RPC endpoint isn’t automatically private: what matters is where it sends your transaction. Compare them in public RPC vs private RPC on Polygon.

No. Hyperstrate only changes how a transaction reaches the network. Your transactions settle on Polygon, and nothing about your contracts, tokens or accounts moves anywhere else.

Anyone who sends transactions where timing and intent matter: trading systems, bots, market makers, wallets, DEXs, DeFi protocols and institutional desks.

MEV (maximal extractable value) is profit taken by inserting, reordering or excluding transactions around yours, for example by frontrunning or sandwiching a swap. On Polygon, MEV protection mostly means keeping a transaction out of the public mempool until it’s included, so bots can’t react to it in advance. It reduces exposure but can’t remove every form of MEV, such as back-running after inclusion. Read MEV protection on Polygon.

Your application signs a transaction as usual and sends it to a private RPC endpoint instead of a public one. The private infrastructure forwards it toward block production without broadcasting it to the public mempool. Once it’s included in a block, it settles normally on Polygon, and Hyperstrate reports each state along the way: received, routed, propagated, included and settled. See why private transaction routing matters.

They reduce the most common kind. Frontrunning bots usually spot pending transactions in the public mempool and pay a higher fee to get ahead of them. A privately submitted transaction isn’t in the public mempool, so those bots can’t react to it in advance. Private submission can’t rule out every party that handles a transaction before inclusion, so keep sensible slippage limits as well. Read how to prevent frontrunning on Polygon.

A sandwich attack targets a pending swap. A bot sees it in the public mempool, buys the same token just before it, which pushes the price up, lets your swap execute at the worse price, then sells straight after for a profit. Your slippage tolerance caps how much you can lose. Keeping swaps out of the public mempool and setting tight slippage both reduce the risk. More in sandwich attacks on Polygon.

Yes, once they’re included in a block. Private submission only affects the time between signing and inclusion: while pending, the transaction isn’t in the public mempool, so it generally won’t appear in public pending-transaction views. After inclusion it shows on Polygonscan with its sender, recipient, input data and fees, like any other Polygon transaction. Private submission doesn’t hide transaction details permanently.

Sign the transaction the way you do today, then submit it to a private RPC endpoint instead of a public one. With Hyperstrate, you point transaction submission at the Hyperstrate RPC endpoint and add your API key; your signing code, contracts and wallet stay the same. Reads such as balances and receipts can stay on your usual provider. Step by step: how to send private transactions on Polygon.

Hyperstrate exposes an authenticated JSON-RPC endpoint, so tools that speak Ethereum JSON-RPC can use it, including ethers.js, viem, web3.js and curl. Use the endpoint for sending transactions, authenticate with your API key, and track each transaction until it settles. No smart contract changes are needed. See the developer examples and the guide to Polygon private transaction APIs.

A trading bot signs transactions with its own key and sends them to the Hyperstrate endpoint instead of a public RPC, usually by changing one URL in its configuration. Its orders then stay out of the public mempool while they’re pending, which makes them harder for other bots to copy or frontrun. Bots should still manage nonces, gas fees and slippage carefully, and watch each transaction until it settles.

No. Private routing happens when a transaction is submitted, so contracts don’t need any changes.

Anything that speaks Ethereum JSON-RPC, including ethers.js, viem, web3.js and plain curl. Backend services and trading bots can submit programmatically.

No. Hyperstrate routes your transaction toward block production, but whether and when it’s included is decided by the network. You’re charged less when a transaction is attempted but doesn’t land, and nothing if it’s never attempted.

It depends on how it fails. If a transaction isn’t included, for example because its fee is too low or its nonce has already been used, it never reaches the chain and can be resubmitted. If it’s included but reverts, it’s recorded onchain as failed and the gas it used is still paid, as with any Polygon transaction. For billing, you pay the lower attempted price when a transaction is attempted but doesn’t land, and nothing if it’s never attempted.

If it was attempted but didn’t land, you pay the lower attempted price, $0.050 on Starter. If it was never attempted, you pay nothing.

Every accepted transaction from your workspace counts toward the same monthly total. Your first 2,500 are billed at Starter prices, the next 7,500 at Growth, the next 40,000 at Scale and the rest at Volume. The count starts again on the 1st of each month (UTC).

It keeps the price it was given when it was first accepted and counts once toward your monthly tier, even if the retry happens next month or after your tier changes.

Other chains can have their own prices. If a chain has no published price, paid submission isn’t available on it yet.