PolyNode RPC

Priority transaction delivery on Polygon — drop-in RPC replacement

Beta — PolyNode RPC is in early access. Contact us for API keys and onboarding.

What is PolyNode RPC?

PolyNode RPC is a high-performance Polygon RPC endpoint with proprietary transaction routing for priority block inclusion. It’s a drop-in replacement for any standard Ethereum RPC — just change the URL.

https://rpc.polynode.dev

Why Use PolyNode RPC?

Priority Execution

90%+ of transactions land as TX #1 (first transaction in block).

Drop-In Compatible

Standard Ethereum JSON-RPC. Works with MetaMask, ethers.js, web3.py, viem, wagmi, Hardhat, Foundry — no SDK needed.

Low-Latency Routing

Proprietary infrastructure minimizes the time between submission and block inclusion.

MEV Protection

Transactions are not broadcast publicly, reducing front-running risk.

How It Works

1. Your transaction arrives at our endpoint via standard eth_sendRawTransaction
2. PolyNode’s routing engine determines the optimal delivery path
3. Your transaction is delivered with priority for fast block inclusion
4. Redundant delivery ensures reliability

The result: your transaction reaches block inclusion faster than transactions submitted through public RPCs.

Quick Start

1. Get an API Key

   Contact us for beta access.

2. Configure Your RPC URL

   Replace your existing Polygon RPC URL with:

   https://rpc.polynode.dev
   
3. Add Authentication

   Include your API key in requests:

   x-api-key: your_api_key
   
4. Send Transactions

   Use any Ethereum library — it just works:

   import { createPublicClient, http } from 'viem'
   import { polygon } from 'viem/chains'
   
   const client = createPublicClient({
     chain: polygon,
     transport: http('https://rpc.polynode.dev', {
       fetchOptions: {
         headers: { 'x-api-key': 'your_api_key' }
       }
     })
   })
   

Supported Methods

PolyNode RPC supports the standard Ethereum JSON-RPC specification. Transaction submission uses our priority routing engine. Core chain data is served directly from our infrastructure. Read methods are served with standard Polygon node responses.

Method	Handling	Description
eth_sendRawTransaction	Priority Engine	Optimized block inclusion
eth_chainId	Local	Returns 0x89 (137)
eth_blockNumber	Local	Latest block number
eth_gasPrice	Local	Calibrated from recent blocks
net_version	Local	Returns 137
net_peerCount	Local	Connected peer count
web3_clientVersion	Local	Returns PolyNode/1.0.0
eth_getBalance	Standard	Account balance queries
eth_getTransactionCount	Standard	Nonce queries
eth_call	Standard	Contract read calls
eth_estimateGas	Standard	Gas estimation
eth_getBlockByNumber	Standard	Block data queries
eth_getTransactionReceipt	Standard	Receipt queries
eth_getLogs	Standard	Log/event queries (requires address filter)
All other methods	Standard	Full JSON-RPC compatibility

Current-state only. State queries like eth_getBalance, eth_getStorageAt, and eth_call only support the latest block tag. Historical state at specific block numbers is not available. Block and transaction data (eth_getBlockByNumber, eth_getTransactionReceipt) works for all blocks.