Amoy RPC Endpoint: Chain Settings, Faucet, and Debugging

Amoy Testnet RPC Decision Checklist

Before you connect to the Amoy testnet, consider these factors to avoid development delays:

Use this checklist when evaluating RPC services for Amoy, including OnFinality's public Amoy endpoint at https://polygon-amoy.api.onfinality.io/public.

---

What Is the Amoy Testnet?

Amoy is the official testnet for Polygon PoS, launched in January 2024 as a replacement for the Mumbai testnet. It uses Ethereum's Sepolia testnet as its root chain (L1) instead of the deprecated Goerli. This ensures long-term viability and alignment with Ethereum's testnet roadmap. Developers use Amoy to deploy and test smart contracts, dApps, and infrastructure in a low-cost, risk-free environment that mirrors Polygon PoS mainnet.

Key chain parameters:

• Network Name: Polygon Amoy
• Chain ID: 80002 (hex: 0x13882)
• Native Currency: POL (test token)
• Block Time: ~2–3 seconds
• Explorer: Amoy Polygonscan
• Consensus: Proof-of-Stake (same as mainnet)

Amoy is the recommended environment for all Polygon PoS testing. Mumbai is deprecated and should not be used for new projects.

---

Amoy RPC Endpoints

Below are commonly used Amoy RPC endpoints. Always verify the latest endpoints from trusted sources.

HTTP Endpoints

WebSocket Endpoints

• wss://polygon-amoy-bor-rpc.publicnode.com
• wss://polygon-amoy.drpc.org
• wss://polygon-amoy.g.alchemy.com/v2/YOUR_API_KEY

Example: JSON-RPC Request via curl

curl -X POST https://polygon-amoy.api.onfinality.io/public \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

Response:

{"jsonrpc":"2.0","id":1,"result":"0x297a7b5"}

Example: Connect with Web3.js (JavaScript)

const Web3 = require('web3');
const web3 = new Web3('https://polygon-amoy.api.onfinality.io/public');

web3.eth.getBlockNumber().then(console.log);
// Output: 43474037 (example)

---

Amoy Faucet

To deploy contracts on Amoy, you need test POL tokens. Use the official Polygon Amoy faucet at faucet.polygon.technology. You can also find community faucets on the Amoy Polygonscan page.

---

Debugging Common Amoy RPC Issues

1. Wrong Chain ID

If your wallet or dApp shows "chain ID mismatch" or transaction fails, check that you are using chain ID 80002 (0x13882). Some tools may default to Mumbai's 80001.

2. Rate Limiting

Public endpoints often impose rate limits (e.g., 10–100 req/s). If you receive 429 Too Many Requests, consider using an API key-based provider or a dedicated node service. OnFinality's public endpoint includes fair usage limits suitable for light testing.

3. WebSocket Disconnections

WebSocket connections may drop after periods of inactivity. Implement reconnection logic in your dApp. Use keep-alive pings every 30 seconds.

4. Missing Archive Data

Some providers disable archive data on testnets. If you need eth_getBalance for historical blocks or eth_call for older state, verify that the provider offers archive support. OnFinality's dedicated node plans include archive access.

5. Faucet Dry

If the faucet runs out of test POL, try alternative faucets or request tokens from the Polygon community Discord.

---

How to Switch from Mumbai to Amoy

1. Update your chain configuration to use chain ID 80002.
2. Replace RPC endpoints with Amoy URLs.
3. Update block explorer links to amoy.polygonscan.com.
4. Obtain test POL from the new faucet (Mumbai tokens are not compatible).
5. Confirm that your smart contracts compile and deploy correctly on Amoy before mainnet.

---

Choosing an RPC Provider for Amoy

For serious testing, consider a managed RPC service. OnFinality supports Polygon Amoy with both a public tier and dedicated node options. Benefits include:

• Load-balanced endpoints with automatic failover
• WebSocket streaming for real-time events
• Archive data on request
• Geographic distribution for low latency
• Usage-based pricing with no surprise limits

Review our RPC pricing and supported networks for details.

---

Key Takeaways

• Amoy is the current Polygon PoS testnet (chain ID 80002), anchored to Sepolia.
• Use the endpoints and code examples above to connect quickly.
• Validate chain ID and faucet availability to avoid common pitfalls.
• For production-level testing, choose a provider with rate limit guarantees, WebSocket support, and archive data.
• OnFinality offers a reliable Amoy RPC endpoint with options to scale.

---

Frequently Asked Questions

What is the Amoy RPC URL?

Public endpoints include https://polygon-amoy.api.onfinality.io/public, https://polygon-amoy-bor-rpc.publicnode.com, and https://polygon-amoy.drpc.org.

What is the Amoy chain ID?

80002 (0x13882 in hex).

Does Amoy use POL or MATIC?

Native currency is POL (test token). Faucets dispense POL.

Is Amoy replacing Mumbai?

Yes. Mumbai is deprecated and relies on Goerli, which is no longer supported. All testing should move to Amoy.

Can I use the same RPC provider for Amoy and Polygon mainnet?

Many providers support both. Check if your provider offers separate endpoints for testnet and mainnet.

---

Last updated: 2025-03-20