Polygon zkEVM Testnet support ends April 6 - migrate to Sepolia
Author: Sameena Shaffeeullah
Polygon zkEVM Cardona is now supported on Alchemy!
We encourage developers to migrate to Cardona as the sustainable path forward for any testing and development needs, as Polygon will stop supporting the zkEVM testnet on April 6th.
We are planning on keeping our testnet nodes for Polygon zkEVM running until this date. However, in the past we have seen extreme instability in networks leading up to deprecation.
While we will do our best to keep it running, we cannot guarantee that this network will be usable until April 6th. It is in your best interest to migrate to Cardona immediately.
If you try to send requests to these nodes after Alchemy support ends, your requests will fail with a DNS resolution error.
All features supported by Alchemy on the zkEVM testnet are also supported on Cardona.
Required steps to migrate to cardona
Follow these 4 steps to migrate to the Cardona testnet:
- Create a new app from the Alchemy dashboard on the Cardona network.
- Change your
API\_URLto your zkEVM Cardona RPC URL:https://polygonzkevm-cardona.g.alchemy.com/v2/ - Deploy your test contract to Cardona.
- Change your tests to use the new contract.
For more detailed instructions, please reference the "How to Deploy a Smart Contract to the Sepolia Testnet" tutorial on our docs.
A note on other chains
Goerli deprecation dates for other chains are up to date on this blog post.
Alchemy Newsletter
Be the first to know about releases
Sign up for our newsletter
Get the latest product updates and resources from Alchemy
By entering your email address, you agree to receive our marketing communications and product updates. You acknowledge that Alchemy processes the information we receive in accordance with our Privacy Notice. You can unsubscribe anytime.
Related articles
Set up Claude Code with Alchemy in 60 seconds
Connect Claude Code to Alchemy with one command. Your coding agent gets live data across 100+ chains: prices, balances, NFTs, transfers, and simulation.
How we rebuild node fleets 15x faster
Most reliability work is invisible. Here is how Alchemy rebuilt node-state recovery with parallel transfer and private networking to keep latency consistent when hardware fails.
How we built low-latency RPC infrastructure
RPC latency is a systems problem, not a single bottleneck. Here is how Alchemy reduced latency across the edge, routing, scaling, node operations, and measurement.