摘要
A Polygon RPC node is an endpoint that lets your dApp or wallet communicate with the Polygon network via JSON-RPC. This page covers the official chain settings for Polygon mainnet and Amoy testnet, lists public and paid RPC providers, and gives a decision checklist for selecting infrastructure that fits your workload.
Polygon RPC Node Decision Checklist
Before selecting a Polygon RPC node provider, evaluate these criteria:
| Criterion | What to check | Why it matters |
|---|---|---|
| Workload type | Read-heavy (data fetching) vs write-heavy (transaction submission) | Public RPCs may throttle writes; dedicated nodes handle high throughput better |
| Rate limits | Requests per second (RPS) and daily/monthly caps | Exceeding limits causes 429 errors and dropped requests |
| Archive data | Does the provider offer archive nodes with historical state? | Needed for block explorers, analytics, and certain dApp features |
| WebSocket support | WSS endpoint for real-time subscriptions | Essential for DEXs, NFT mints, and event listeners |
| Geographic distribution | Nodes in multiple regions | Reduces latency and improves failover |
| Testnet availability | Amoy testnet RPC for development | Required for staging and testing before mainnet deployment |
| Pricing model | Pay-as-you-go vs flat monthly fee vs free tier | Match your budget and expected request volume |
| Uptime SLA | Provider's historical uptime (not guaranteed) | Frequent downtime breaks user experience |
Polygon Network Overview
Polygon (formerly Matic) is a Layer-2 scaling solution for Ethereum that uses a sidechain architecture with a Proof-of-Stake consensus. It offers low transaction fees and fast finality, making it popular for DeFi, gaming, and NFT applications. To interact with Polygon, your application needs an RPC node—either one you run yourself or one provided by a third-party service.
Polygon Chain Settings
Mainnet
| Property | Value |
|---|---|
| Network name | Polygon Mainnet |
| Parent chain | Ethereum |
| Chain ID | 137 (0x89) |
| Gas token | POL |
| RPC endpoint | https://polygon-rpc.com (public) |
| WSS endpoint | wss://polygon-rpc.com (public) |
| Block explorer | https://polygonscan.com |
Amoy Testnet
| Property | Value |
|---|---|
| Network name | Amoy |
| Parent chain | Sepolia |
| Chain ID | 80002 |
| Gas token | POL |
| RPC endpoint | https://rpc-amoy.polygon.technology (public) |
| WSS endpoint | wss://rpc-amoy.polygon.technology (public) |
| Block explorer | https://amoy.polygonscan.com |
| Faucet | https://faucet.polygon.technology |
Public vs Paid RPC Nodes
Public (Free) RPC Nodes
Public RPC endpoints are free to use but often have rate limits, no reliability expectations, and may throttle heavy usage. They are suitable for development, testing, and low-traffic applications. Common public endpoints include:
- https://polygon-rpc.com
- https://polygon-bor-rpc.publicnode.com
- https://polygon.api.onfinality.io/public
Paid RPC Nodes
Paid services offer higher rate limits, dedicated nodes, archive data, WebSocket support, and SLAs. They are recommended for production dApps with significant traffic. Providers include:
- OnFinality (shared and dedicated nodes)
- Alchemy
- Infura
- QuickNode
- Chainstack
- dRPC
How to Connect to a Polygon RPC Node
Using curl
curl https://polygon-rpc.com \
-X POST \
-H "Content-Type: application/json" \
--data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'
Using Web3.js (JavaScript)
const Web3 = require('web3');
const web3 = new Web3('https://polygon-rpc.com');
web3.eth.getBlockNumber().then(console.log);
Using ethers.js (JavaScript)
const { ethers } = require('ethers');
const provider = new ethers.providers.JsonRpcProvider('https://polygon-rpc.com');
provider.getBlockNumber().then(console.log);
Common RPC Methods for Polygon
Polygon supports standard Ethereum JSON-RPC methods. Some frequently used ones:
eth_blockNumber– Get the latest block numbereth_getBalance– Get POL balance of an addresseth_call– Execute a contract call without creating a transactioneth_sendRawTransaction– Submit a signed transactioneth_gasPrice– Get current gas priceeth_getTransactionReceipt– Get receipt of a transaction
Choosing the Right Provider
When to Use a Public Node
- Prototyping and hackathons
- Low-traffic personal projects
- Read-only queries where occasional rate limiting is acceptable
When to Use a Paid Provider
- Production dApps with real users
- High-frequency trading or DeFi bots
- Applications requiring archive data or trace API
- Need for WebSocket subscriptions
- Requirement for dedicated node resources
Dedicated vs Shared Nodes
- Shared nodes: Multiple users share the same node. Lower cost but risk of noisy neighbors.
- Dedicated nodes: A node reserved for your use. Higher cost but consistent performance, full control over resources, and ability to use custom RPC methods.
Troubleshooting Common Issues
Rate Limiting (HTTP 429)
If you receive 429 errors, your requests are being throttled. Solutions:
- Upgrade to a paid plan with higher RPS
- Implement request queuing or batching
- Use a dedicated node
Connection Timeouts
- Check your internet connection
- Ensure the RPC URL is correct (mainnet vs testnet)
- Try a different provider
Invalid Chain ID
- Make sure your wallet or dApp is configured with chain ID 137 (mainnet) or 80002 (Amoy)
- Verify the RPC endpoint matches the intended network
Key Takeaways
- Polygon mainnet uses chain ID 137 and POL as gas token; Amoy testnet uses chain ID 80002.
- Public RPC nodes are free but limited; paid providers offer scalability and reliability.
- Choose a provider based on workload type, rate limits, archive needs, and geographic coverage.
- Always test on Amoy testnet before deploying to mainnet.
- For production, consider dedicated nodes or services with SLAs.
Frequently Asked Questions
What is a Polygon RPC node?
A Polygon RPC node is a server that exposes the Polygon blockchain via JSON-RPC, allowing applications to read data and submit transactions.
Can I run my own Polygon node?
Yes, you can run a full node using Polygon's client software (Bor and Heimdall). However, it requires significant hardware and maintenance effort.
What is the difference between Bor and Heimdall?
Bor is the block producer layer (execution layer), while Heimdall is the consensus layer that manages validators and checkpoints to Ethereum.
How do I get free POL for Amoy testnet?
Use the official Polygon faucet at https://faucet.polygon.technology.
Does OnFinality support Polygon?
Yes, OnFinality provides Polygon RPC endpoints and dedicated node options. See the Polygon network page for details.
What is the best Polygon RPC provider?
There is no single "best" provider—it depends on your requirements. Evaluate based on the checklist above and consider testing multiple providers.
For more information, check our RPC pricing and supported networks.