Skip to main content

Migrating to Etherlink Shadownet Testnet

Etherlink has migrated to a new testnet. This new testnet is based on the Tezos Shadownet testnet, just as the legacy testnet was based on the Tezos Ghostnet testnet. For this reason, the new test network is referred to as "Etherlink Shadownet Testnet" and the legacy test network is referred in this documentation as "Etherlink Ghostnet Testnet." This migration ensures that Etherlink's primary Testnet is aligned with the most up-to-date long-running Tezos test network that is similar to Mainnet.

Etherlink Ghostnet Testnet has sunset and is no longer available.

This page gives the details of the migration, including milestones, calls to action, and the current status. It is intended for all the Etherlink partners such as infrastructure providers, node operators, and application builders.

Key information

Here are some important pieces of information for Etherlink Shadownet Testnet:

For more technical details about this network, see Network information.

Rationale

This migration ensures better testnet parity with Etherlink Mainnet, ensuring a much smoother launch of applications and services in production.

This paves the way for more partners to bring their applications to Etherlink, by concretely ensuring:

  • Earlier Etherlink Stack requirement forecasts
  • Better pre-live simulations
  • Better overall builder experience

Tezos L1 Ghostnet has also been discontinued.

Migration steps

The migration has been delivered in the following phases:

PhaseActivitiesStatus

Phase 1
Sep-Oct 2025

  • Sequencer & Relay nodes are set up
  • Etherlink Shadownet genesis takes place
  • Documentation for infrastructure providers issued
✅ Complete

Phase 2
Oct-Nov 2025

  • JSON-RPC API providers & blockchain indexers nodes setup
  • Block Explorer
  • Oracles
  • Network public goods: deployment of tokens, utility contracts (multicall3, create3 factories etc)
  • Smart Rollup node snapshot service available
  • EVM node snapshot service available
  • Updates to developer SDKs (viem, chainlist, etc.)
  • Network monitoring infrastructure
✅ Complete

Phase 3
Nov-Dec 2025

  • Faucet UI
  • Safe multisig service
  • Developers that have deployed apps to Ghostnet migrate them to Shadownet
✅ Complete

Phase 4
Dec 2025-Jan 2026

  • Shadownet Tezos Bridge
  • EVM Bridge
  • Final app testing
  • Redirection of testnet URLs to Shadownet
  • Planned sunset of Etherlink Ghostnet Testnet, aligned with deprecation of Tezos L1 Ghostnet
  • Sunset of Etherlink Ghostnet ecosystem infrastructure services and dapps
  • Etherlink Ghostnet Testnet sequencer shut down
✅ Complete

Calls to action

This section is meant for guiding the different categories of partners into action.

For node operators

If you run EVM nodes on the existing Ghostnet Testnet, please carry out the following tasks:

ACTION REQUIRED:

  1. Set up new Shadownet EVM nodes following the instructions in Running an Etherlink EVM node.
  2. If you run Smart Rollup nodes, follow the instructions for setting up your Etherlink Shadownet Smart Rollup Node.
  3. If you run L1 Octez nodes, then follow these instructions to install Octez for Tezos L1 Shadownet testnet.
  4. Carry out end-to-end testing to ensure performance is in line with your Ghostnet EVM node.
  5. (For commercial RPC providers) Inform your users about availability of the new nodes.

For infrastructure providers

If you were operating infrastructure services for Etherlink Ghostnet Testnet, please prepare for these typical migration tasks:

  • Check for any missing on-chain or off-chain dependencies and escalate with the Etherlink team
  • Provision new infrastructure/hosts as needed
  • Update JSON-RPC API endpoints from Etherlink Ghostnet to Etherlink Shadownet
  • Obtain Etherlink Shadownet tez from the faucet
  • Redeploy contracts to Etherlink Shadownet
  • Update databases with Etherlink Shadownet data and addresses
  • Update your apps to use the chain ID of Etherlink Shadownet
  • Update your web3 SDKs to use Etherlink Shadownet
  • End-to-end testing/QA
  • Deployment and release to end-users

For developers

If you were operating a dApp or marketplace on Etherlink Ghostnet Testnet for testing purposes, there should be no change in app behavior following the migration to Shadownet.

Migration typically involves the following steps:

  • Check for any missing on-chain or off-chain dependencies and escalate with the Etherlink team
  • Provision new infrastructure/hosts as needed
  • Update JSON-RPC API endpoints from Etherlink Ghostnet to Etherlink Shadownet.
  • Obtain Etherlink Shadownet tez from the faucet
  • Redeploy contracts to Etherlink Shadownet
  • Migrate to new endpoints for data indexers or APIs
  • Update databases with Etherlink Shadownet data
  • Update your apps to use the new chainId
  • Update your web3 SDKs to use Etherlink Shadownet
  • End-to-end testing/QA
  • Deployment and release to end-users

Getting help

Regular updates have been announced via the following channels:

For support, or if you have any questions about the testnet migration, please reach out to our team via existing direct channels or on the Etherlink Discord.

arrow icon

Prev

Monitoring Etherlink nodes

Next

arrow icon
Exchanges