Polygon Retires Amoy RPC, Mainnet Cutoff Set for July 31

Polygon Amoy RPC Retirement Starts the Migration Clock

Amoy is Polygon’s testnet, a place where developers can test deployments and transactions without spending real assets. Polygon’s docs list its parent chain as Sepolia and provide a faucet for test tokens. The retiring address is not a smart contract, bridge or validator set. It is a public access service run by Polygon.

That distinction sets the scope. Teams that use a managed provider, their own node or another public RPC may have nothing to change. Teams that pasted the old endpoint into a wallet configuration, environment variable, deployment script or monitoring job need to replace it and check the dependent service.

Polygon’s notice directs users to its RPC endpoint reference. The page identifies public alternatives including dRPC, Tenderly, Allnodes, Tatum, Nodies and 1RPC, while also listing paid services such as Alchemy, Infura, QuickNode and Amazon Managed Blockchain. Public services can impose rate limits or traffic restrictions, the docs say, so a high-volume application may need a different service level from a hobby test deployment.

The timing makes Amoy more than housekeeping. A testnet is where app teams find broken transaction flows, WebSocket subscriptions and chain-ID mistakes before they reach mainnet. Switching there first gives a team a live check on its settings before the mainnet deadline arrives two weeks later.

Polygon’s status page showed its systems as operational when checked Friday. That supports the narrow reading: this is a scheduled retirement of specific free endpoints, not a reported problem with Polygon mainnet or Amoy block production.

Polygon Mainnet RPC Deadline Is July 31

The larger deadline is for polygon-rpc.com, the Polygon-operated public mainnet address. Polygon’s notice says it will be deprecated after July 31 and advises applications, wallets and services to migrate before then to avoid disruption.

For a typical application, the first step is an inventory. Teams should search repositories, deployment variables, secrets managers, monitoring configurations and third-party integrations for the outgoing URL. A replacement should be tested for basic reads, transaction submission, block subscriptions and rate-limit behavior before it is made the production default.

The replacement is not necessarily one-for-one. An endpoint that works for occasional wallet reads can be unsuitable for a market-data service making many calls per second. WebSocket support, archive-data needs, geographic latency, authentication, uptime terms and billing can all differ. Polygon’s documentation separates public RPCs from enterprise-grade paid services for that reason.

The change comes weeks after Polygon completed the sunset of its zkEVM Mainnet Beta. That earlier event required a different response because it involved a sequencer, bridge claims and some contract-held funds. As Daily Crypto Briefs reported in Polygon’s zkEVM withdrawal process, users with balances in DeFi contracts needed protocol-specific exits. This RPC retirement does not alter mainnet balances or create a claim process.

It also differs from a chain-level stall. When Base halted after an invalid block, the immediate issue was block production and canonical state. Here, the chain can remain healthy while an individual service loses the route it used to reach that state.

Apps Need a Fallback Plan Beyond Polygon RPC

The broader lesson is that a free default endpoint should not become an invisible single point of failure. A product that treats its RPC provider as replaceable infrastructure can rotate it with limited user impact. A product that embeds one address across a codebase may discover the dependency only when its users see blank balances or failed requests.

The Polygon developer docs now surface public alternatives for both networks. That is useful, but it does not guarantee the same throughput, retention, reliability or request limits as the old Polygon-operated service. Teams should verify the terms and observed behavior of the provider they choose rather than assuming that every public URL is equivalent.

For wallets and end users, the most useful check is simpler: do not enter a random replacement RPC supplied in a chat room or social post. Use the addresses in official documentation or a provider’s own documentation, and confirm that a wallet is set to Polygon mainnet chain ID 137 or Amoy chain ID 80002 as appropriate.

The transition also adds another operational test for apps that are positioning Polygon as a payments and consumer rail. Daily Crypto Briefs recently covered machine-payment credentials involving Polygon; products built for continuous payments need redundancy at the provider layer as much as they need low transaction fees.

Crypto market sentiment remained cautious. The Crypto Fear and Greed Index read 27, or Fear, on July 17, a broad measure that does not isolate demand for POL or Polygon infrastructure.

The immediate watchpoints are clear: whether any major application announces a migration issue after the Amoy retirement, and whether teams finish moving from polygon-rpc.com before July 31. Polygon has not announced a chain shutdown or token change. Its message is narrower, but for an app with the old URL embedded in production, the deadline is operationally real.