Network
Launch Date
Consensus
Note
Sepolia
Oct 2021
PoW
Like-for-like representation of Ethereum
Görli
Jan 2019
PoA
Proof-of-Authority
Kiln
Mar 2022
PoS
Post-Merge (for ETH2), shadow fork of the mainnet
Kintsugi
Dec 2021
PoS
DEPRECATED, use Kiln; post-Merge (for ETH2)
Ropsten
Nov 2016
PoW
DEPRECATED, use Sepolia; the Merge to happen on Jun 8, 2022
Rinkeby
Apr 2017
PoA
DEPRECATED, use Görli and Görli Faucet
Kovan
Mar 2017
PoA
DEPRECATED, use Sepolia or Görli
List of active and deprecated Ethereum testnets, including Kintsugi.
Features
Optimistic rollup 
ZK-rollup 
Proof
Uses fraud proofs to prove transaction validity. 
Uses validity (zero-knowledge) proofs to prove transaction validity. 
Capital efficiency
Requires waiting through a 1-week delay (dispute period) before withdrawing funds. 
Users can withdraw funds immediately because validity proofs provide incontrovertible evidence of the authenticity of off-chain transactions. 
Data compression
Publishes full transaction data as calldata to Ethereum Mainnet, which increases rollup costs. 
Doesn't need to publish transaction data on Ethereum because ZK-SNARKs and ZK-STARKs already guarantee the accuracy of the rollup state. 
EVM compatibility
Uses a simulation of the Ethereum Virtual Machine (EVM), which allows it to run arbitrary logic and support smart contracts. 
Doesn't widely support EVM computation, although a few EVM-compatible ZK-rollups have appeared. 
Rollup costs
Reduces costs since it publishes minimal data on Ethereum and doesn't have to post proofs for transactions, except in special circumstances. 
Faces higher overhead from costs involved in generating and verifying proofs for every transaction block. ZK proofs require specialized, expensive hardware to create and have high on-chain verification costs. 
Trust assumptions
Doesn't require a trusted setup. 
Requires a trusted setup to work. 
Liveness requirements
Verifiers are needed to keep tabs on the actual rollup state and the one referenced in the state root to detect fraud. 
Users don't need someone to watch the L2 chain to detect fraud. 
Security properties 
Relies on cryptoeconomic incentives to assure users of rollup security. 
Relies on cryptographic guarantees for security. 
Start building
on Alchemy.
Sign up for free
Start building on Optimism.
Sign up for free
Start building on Arbitrum.
Sign up for free
Start building on Ethereum.
Sign up for free
Start building on Polygon.
Sign up for free
Start building on Starknet.
Sign up for free
Start building on Flow.
Sign up for free
kiln faucet
Get free Kiln ETH.
Start building today
Goerli faucet
Get free Goerli ETH.
Start building today
mumbai faucet
Get free Mumbai Matic.
Start building today
rinkeby faucet
Get free Rinkeby
ETH.
Start building today
Start building on Ethereum.
Get started for free
Start building on Ethereum.
Get started for free
Start building on Flow.
Get started for free
Start building on Polygon.
Get started for free
Start building on Starknet.
Get started for free
Start building on Optimism.
Get started for free
Start building on Solana.
Get started for free
Start building on Solana.
Sign up for beta access
Start building on Solana.
Join the waitlist
Arbitrum logo
Start building on Arbitrum.
Get started for free
Learn
Solidity at
Alchemy
University
Get started today
curl 
https://release.solana.com/v1.10.32/solana-install-init-x86_64-pc-windows-msvc.exe 
--output 
C:\solana-install-tmp\solana-install-init.exe 
--create-dirs
Testnets
ROPSTEN TESTNET MIGRATION

How to Migrate from Ropsten to Goerli

Last Updated:
June 20, 2022

With the recent deprecation of the Ropsten test network, and the upcoming deprecation of the Rinkeby testnet, developers should be prepared to migrate dApps off of testnets that will not be supported after the Ethereum merge. Before Ethereum's existing Proof-of-Work blockchain merges with the new Proof-of-Stake Beacon Chain, dApps should deploy their smart contracts on the Goerli testnet which will be maintained after The Merge is complete.

Testnets are important web3 developer tools for testing the smart contracts used in decentralized applications and the configurations of nodes running various types of client software. With the Ethereum Merge timeline underway, the recommended testnets that engineers should use are changing.

What testnets are being deprecated?

To date, the primary testnets that have been deprecated include Kovan, Ropsten, and Kintsugi. Rinkeby will be deprecated later this year, and the Prater testnet will be merged with Goerli. The Sepolia testnet will continue to be maintained after the merge so client developers can continue to test their nodes.

Alchemy will support the Ropsten and Kovan testnets until July 1st, 2022. Both of these testnets have already been deprecated by the Ethereum Foundation and the larger Ethereum community. Kovan has been deprecated for the last year, whereas the Ropsten testnet recently completed its merge on June 8th as a planning exercise ahead of the mainnet merge, which is expected to happen later this year.

What happens after a testnet is deprecated?

After a testnet is deprecated, no additional client updates will be provided by the community, and the software used to run testnet nodes will not actively be maintained. This means these networks will no longer serve as a safe or accurate environment for testing applications.

Once a testnet is on the deprecation path, while some node infrastructure providers might continue running nodes, they will eventually lose parity with the Ethereum Virtual Machine (EVM). In other words, the EVM execution will drift apart from the production EVM execution environment on mainnet.

Because Ropsten and Kovan are no longer actively maintained, they are no longer good places to test smart contracts.

What is the difference between deprecated and sunset?

Deprecation means a testnet will no longer be supported by the community, whereas sunset means the testnet no longer exists (i.e. there are no longer nodes running the network). Ropsten and Kovan are not sunset yet, but they are deprecated, which means no more upgrades or bug fixes will be deployed to maintain the node client software.

What testnets should I use instead of Ropsten?

The two testnets that Alchemy and the Ethereum Foundation recommend using are Goerli and Sepolia. These two testnets will be maintained after The Merge, and it is where dApp and client developers should migrate to from Ropsten, Kovan, and Rinkeby.

For Ethereum application developers building dApps like DeFi protocols, NFT marketplaces, and web3 projects, Goerli is the recommended testnet. This will be the majority of builders in the web3 space.

For engineers building, maintaining, and testing node client software, Sepolia is the recommended testnet to use during and after the merge because it is a Proof-of-Work (PoW) testnet that most similarly reflects the current state of the Ethereum mainnet.

Although the Rinkeby testnet won't be deprecated until later in 2022, it is recommended that web3 development teams using Rinkeby start planning, testing, and re-deploying their contracts to the Goerli testnet as well.

How to Migrate from Ropsten to Goerli

To migrate from Ropsten to the Goerli testnet create a new app in the Alchemy dashboard for the Ethereum blockchain and the Goerli test network.

Creating a new Goerli app in the Alchemy dashboard.

Then, copy the Goerli RPC URL for your app. This is what the new Goerli RPC URL will look like: https://eth-goerli.alchemyapi.io/v2/<your api key>

View the Goerli RPC URL in the Alchemy dashboard.

Once you've created a new Goerli RPC URL, get goETH from a Goerli faucet. This fake ETH will be used to pay for transaction on the Goerli testnet.

By signing up for a free Alchemy account you can request 0.05 goETH per day. If you need more goETH, please contact [email protected]

Goerli faucet for getting goETH.

Now that you have goETH, deploy your smart contract in your new Goerli app with Alchemy the same way you deployed your Ropsten app.

Once your app is deployed on Goerli, you can run tests, fine-tune code, and iterate on your product the same way you did when testing dApps on other testnets.

Things to Consider Before Migrating from Ropsten to Goerli

Before migrating smart contracts from Ropsten to Goerli, dApp developers should consider their:

1. Product roadmap

2. Upcoming deadlines

3. Testing and verification needs

4. Smart contract dependencies

By considering these four areas, engineers can ensure their dApps work as they are expected to work on Goerli, and complete the migration from Ropsten before the deprecated testnet begins to lose parity with Ethereum.

ALCHEMY SUPERNODE - ETHEREUM NODE API

Scale to any size, without any errors

Alchemy Supernode finally makes it possible to scale blockchain applications without all the headaches. Plus, our legendary support will guide you every step of the way.

Get started for free
Supernode footer
Testnets
ROPSTEN TESTNET MIGRATION

How to Migrate from Ropsten to Goerli

Last Updated:
June 20, 2022
Don't miss an update
Sign up for our newsletter to get alpha, key insights, and killer resources.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

With the recent deprecation of the Ropsten test network, and the upcoming deprecation of the Rinkeby testnet, developers should be prepared to migrate dApps off of testnets that will not be supported after the Ethereum merge. Before Ethereum's existing Proof-of-Work blockchain merges with the new Proof-of-Stake Beacon Chain, dApps should deploy their smart contracts on the Goerli testnet which will be maintained after The Merge is complete.

Testnets are important web3 developer tools for testing the smart contracts used in decentralized applications and the configurations of nodes running various types of client software. With the Ethereum Merge timeline underway, the recommended testnets that engineers should use are changing.

What testnets are being deprecated?

To date, the primary testnets that have been deprecated include Kovan, Ropsten, and Kintsugi. Rinkeby will be deprecated later this year, and the Prater testnet will be merged with Goerli. The Sepolia testnet will continue to be maintained after the merge so client developers can continue to test their nodes.

Alchemy will support the Ropsten and Kovan testnets until July 1st, 2022. Both of these testnets have already been deprecated by the Ethereum Foundation and the larger Ethereum community. Kovan has been deprecated for the last year, whereas the Ropsten testnet recently completed its merge on June 8th as a planning exercise ahead of the mainnet merge, which is expected to happen later this year.

What happens after a testnet is deprecated?

After a testnet is deprecated, no additional client updates will be provided by the community, and the software used to run testnet nodes will not actively be maintained. This means these networks will no longer serve as a safe or accurate environment for testing applications.

Once a testnet is on the deprecation path, while some node infrastructure providers might continue running nodes, they will eventually lose parity with the Ethereum Virtual Machine (EVM). In other words, the EVM execution will drift apart from the production EVM execution environment on mainnet.

Because Ropsten and Kovan are no longer actively maintained, they are no longer good places to test smart contracts.

What is the difference between deprecated and sunset?

Deprecation means a testnet will no longer be supported by the community, whereas sunset means the testnet no longer exists (i.e. there are no longer nodes running the network). Ropsten and Kovan are not sunset yet, but they are deprecated, which means no more upgrades or bug fixes will be deployed to maintain the node client software.

What testnets should I use instead of Ropsten?

The two testnets that Alchemy and the Ethereum Foundation recommend using are Goerli and Sepolia. These two testnets will be maintained after The Merge, and it is where dApp and client developers should migrate to from Ropsten, Kovan, and Rinkeby.

For Ethereum application developers building dApps like DeFi protocols, NFT marketplaces, and web3 projects, Goerli is the recommended testnet. This will be the majority of builders in the web3 space.

For engineers building, maintaining, and testing node client software, Sepolia is the recommended testnet to use during and after the merge because it is a Proof-of-Work (PoW) testnet that most similarly reflects the current state of the Ethereum mainnet.

Although the Rinkeby testnet won't be deprecated until later in 2022, it is recommended that web3 development teams using Rinkeby start planning, testing, and re-deploying their contracts to the Goerli testnet as well.

How to Migrate from Ropsten to Goerli

To migrate from Ropsten to the Goerli testnet create a new app in the Alchemy dashboard for the Ethereum blockchain and the Goerli test network.

Creating a new Goerli app in the Alchemy dashboard.

Then, copy the Goerli RPC URL for your app. This is what the new Goerli RPC URL will look like: https://eth-goerli.alchemyapi.io/v2/<your api key>

View the Goerli RPC URL in the Alchemy dashboard.

Once you've created a new Goerli RPC URL, get goETH from a Goerli faucet. This fake ETH will be used to pay for transaction on the Goerli testnet.

By signing up for a free Alchemy account you can request 0.05 goETH per day. If you need more goETH, please contact [email protected]

Goerli faucet for getting goETH.

Now that you have goETH, deploy your smart contract in your new Goerli app with Alchemy the same way you deployed your Ropsten app.

Once your app is deployed on Goerli, you can run tests, fine-tune code, and iterate on your product the same way you did when testing dApps on other testnets.

Things to Consider Before Migrating from Ropsten to Goerli

Before migrating smart contracts from Ropsten to Goerli, dApp developers should consider their:

1. Product roadmap

2. Upcoming deadlines

3. Testing and verification needs

4. Smart contract dependencies

By considering these four areas, engineers can ensure their dApps work as they are expected to work on Goerli, and complete the migration from Ropsten before the deprecated testnet begins to lose parity with Ethereum.

With the recent deprecation of the Ropsten test network, and the upcoming deprecation of the Rinkeby testnet, developers should be prepared to migrate dApps off of testnets that will not be supported after the Ethereum merge. Before Ethereum's existing Proof-of-Work blockchain merges with the new Proof-of-Stake Beacon Chain, dApps should deploy their smart contracts on the Goerli testnet which will be maintained after The Merge is complete.

Testnets are important web3 developer tools for testing the smart contracts used in decentralized applications and the configurations of nodes running various types of client software. With the Ethereum Merge timeline underway, the recommended testnets that engineers should use are changing.

What testnets are being deprecated?

To date, the primary testnets that have been deprecated include Kovan, Ropsten, and Kintsugi. Rinkeby will be deprecated later this year, and the Prater testnet will be merged with Goerli. The Sepolia testnet will continue to be maintained after the merge so client developers can continue to test their nodes.

Alchemy will support the Ropsten and Kovan testnets until July 1st, 2022. Both of these testnets have already been deprecated by the Ethereum Foundation and the larger Ethereum community. Kovan has been deprecated for the last year, whereas the Ropsten testnet recently completed its merge on June 8th as a planning exercise ahead of the mainnet merge, which is expected to happen later this year.

What happens after a testnet is deprecated?

After a testnet is deprecated, no additional client updates will be provided by the community, and the software used to run testnet nodes will not actively be maintained. This means these networks will no longer serve as a safe or accurate environment for testing applications.

Once a testnet is on the deprecation path, while some node infrastructure providers might continue running nodes, they will eventually lose parity with the Ethereum Virtual Machine (EVM). In other words, the EVM execution will drift apart from the production EVM execution environment on mainnet.

Because Ropsten and Kovan are no longer actively maintained, they are no longer good places to test smart contracts.

What is the difference between deprecated and sunset?

Deprecation means a testnet will no longer be supported by the community, whereas sunset means the testnet no longer exists (i.e. there are no longer nodes running the network). Ropsten and Kovan are not sunset yet, but they are deprecated, which means no more upgrades or bug fixes will be deployed to maintain the node client software.

What testnets should I use instead of Ropsten?

The two testnets that Alchemy and the Ethereum Foundation recommend using are Goerli and Sepolia. These two testnets will be maintained after The Merge, and it is where dApp and client developers should migrate to from Ropsten, Kovan, and Rinkeby.

For Ethereum application developers building dApps like DeFi protocols, NFT marketplaces, and web3 projects, Goerli is the recommended testnet. This will be the majority of builders in the web3 space.

For engineers building, maintaining, and testing node client software, Sepolia is the recommended testnet to use during and after the merge because it is a Proof-of-Work (PoW) testnet that most similarly reflects the current state of the Ethereum mainnet.

Although the Rinkeby testnet won't be deprecated until later in 2022, it is recommended that web3 development teams using Rinkeby start planning, testing, and re-deploying their contracts to the Goerli testnet as well.

How to Migrate from Ropsten to Goerli

To migrate from Ropsten to the Goerli testnet create a new app in the Alchemy dashboard for the Ethereum blockchain and the Goerli test network.

Creating a new Goerli app in the Alchemy dashboard.

Then, copy the Goerli RPC URL for your app. This is what the new Goerli RPC URL will look like: https://eth-goerli.alchemyapi.io/v2/<your api key>

View the Goerli RPC URL in the Alchemy dashboard.

Once you've created a new Goerli RPC URL, get goETH from a Goerli faucet. This fake ETH will be used to pay for transaction on the Goerli testnet.

By signing up for a free Alchemy account you can request 0.05 goETH per day. If you need more goETH, please contact [email protected]

Goerli faucet for getting goETH.

Now that you have goETH, deploy your smart contract in your new Goerli app with Alchemy the same way you deployed your Ropsten app.

Once your app is deployed on Goerli, you can run tests, fine-tune code, and iterate on your product the same way you did when testing dApps on other testnets.

Things to Consider Before Migrating from Ropsten to Goerli

Before migrating smart contracts from Ropsten to Goerli, dApp developers should consider their:

1. Product roadmap

2. Upcoming deadlines

3. Testing and verification needs

4. Smart contract dependencies

By considering these four areas, engineers can ensure their dApps work as they are expected to work on Goerli, and complete the migration from Ropsten before the deprecated testnet begins to lose parity with Ethereum.

Build web3 with Alchemy

Alchemy combines the most powerful web3 developer products and tools with resources, community and legendary support.

Get started for free