Polygon RPC Endpoints

Dwellir provides Polygon PoS RPC endpoints at https://api-polygon-mainnet-full.n.dwellir.com/<your-api-key> for mainnet (Chain ID 137). The Amoy testnet uses Chain ID 80002. Replace <your-api-key> with the key from your Dwellir dashboard.

Yes. WebSocket endpoints are available at wss://api-polygon-mainnet-full.n.dwellir.com/<your-api-key> for mainnet. Use WebSockets for real-time subscriptions like eth_subscribe for new blocks, pending transactions, and log events. Polygon's ~2 second block times make WebSocket subscriptions particularly useful for responsive dApps.

Our standard Polygon endpoints run full nodes that retain recent blockchain state. Full nodes can query current balances and execute transactions but may not have complete state from early blocks. For deep historical queries (e.g., eth_call at arbitrary past blocks), contact our team about dedicated archive node options.

1. Sign up at dwellir.com and retrieve your API key from the dashboard. 2. Replace your current RPC URL (e.g., https://polygon-rpc.com) with https://api-polygon-mainnet-full.n.dwellir.com/<your-api-key>. 3. For WebSocket connections, use wss://api-polygon-mainnet-full.n.dwellir.com/<your-api-key>. The API is fully compatible with standard Ethereum JSON-RPC methods.

Polygon PoS Mainnet uses Chain ID 137 with POL as the native token and ~2 second block times. The Amoy testnet (replacing Mumbai) uses Chain ID 80002 with POL as the test token and Sepolia as its L1 root chain. Polygon uses a PoS consensus with Heimdall and Bor architecture. Block explorers: polygonscan.com (mainnet) and amoy.polygonscan.com (Amoy).

Dwellir's Polygon endpoints are fully compatible with standard EVM tooling including Web3.js, ethers.js, viem, and Web3.py. Development frameworks like Hardhat, Foundry, and Truffle work seamlessly. The Matic.js library provides additional Polygon-specific functionality. Simply configure your provider with the Dwellir RPC URL and your API key.

This error occurs when trying to replace a pending transaction with insufficient gas price increase. Polygon requires replacement transactions to have gas prices at least 10% higher than the original. To fix: 1) Get the pending transaction's gas price, 2) Submit a new transaction with the same nonce but 10-20% higher maxPriorityFeePerGas and maxFeePerGas. To cancel a stuck transaction, send 0 POL to yourself with the same nonce and higher gas. Use eth_getTransactionCount with 'pending' parameter to track your current nonce.

Polygon's ~2 second block times and high throughput lead to rapid gas price fluctuations. Unlike Ethereum, Polygon often has very low base fees (sometimes under 30 gwei) but can spike during congestion. For reliable transactions: 1) Always fetch current gas prices via eth_gasPrice or eth_feeHistory, 2) Set maxFeePerGas at least 30% above current base fee to handle spikes, 3) Use reasonable maxPriorityFeePerGas (typically 30-50 gwei) to incentivize inclusion. The Polygon gas station API can help estimate optimal fees.