Blog
Private transactions on Polygon are normal signed transactions that skip the public mempool on their way to a block. Here is how they work, what they protect and where their…
A step-by-step developer tutorial: build and sign a Polygon transaction locally, submit it to a private RPC endpoint, and track it until it is final, with ethers.js, viem and…
What a Polygon private RPC actually does with your transaction, how it differs from a standard RPC endpoint, what it can and cannot hide, and the questions to ask before you…
What MEV is, how transaction ordering on Polygon creates it, how private submission reduces your exposure, and the honest limits of any MEV protection.
How frontrunning works on Polygon, how to spot it on Polygonscan, and practical ways to reduce it, from private submission and tight slippage to safer contract design.
How sandwich attacks work on Polygon DEXs, why your slippage tolerance is effectively the attacker's budget, how to spot one on Polygonscan, and practical ways to reduce the risk.
Public, dedicated and private RPC endpoints on Polygon compared side by side, why a dedicated endpoint is not automatically private, and how to combine them for reads and writes.
A developer's guide to Polygon private transaction APIs: authentication, signed transactions, nonce and fee handling, status tracking, idempotent retries and the errors you will…
For DeFi traders and bots on Polygon, the route a transaction takes affects the price it gets. Here is how public mempool exposure costs traders, where private routing helps, and…
Follow a Polygon transaction from creation and signing through the mempool to block inclusion and finality, and learn why transactions get stuck, dropped or replaced.
Hyperstrate
One authenticated JSON-RPC endpoint for private transaction submission on Polygon. Keep your signing code, contracts and wallets as they are.
