Ethereum networks (mainnet, testnet) in Blockchain / Solidity - Deep Dive

Overview - Ethereum networks (mainnet, testnet)

What is it?

Ethereum networks are different versions of the Ethereum blockchain used for various purposes. The mainnet is the real Ethereum network where actual value and transactions happen. Testnets are separate networks that mimic the mainnet but use fake currency for testing and development. They help developers try out new code safely without risking real money.

Why it matters

Without separate Ethereum networks, developers would have to test their programs directly on the mainnet, risking real money and causing potential problems for users. Testnets allow safe experimentation and debugging, which keeps the mainnet stable and secure. This separation helps the Ethereum ecosystem grow without breaking things for real users.

Where it fits

Before learning about Ethereum networks, you should understand basic blockchain concepts like blocks, transactions, and smart contracts. After this, you can explore how to deploy and interact with smart contracts on different networks and learn about network-specific tools and wallets.

Mental Model

Core Idea

Ethereum networks are like different playgrounds: the mainnet is the real playground with real toys, while testnets are practice playgrounds with pretend toys for safe learning.

Think of it like...

Imagine you want to try a new recipe. The mainnet is like cooking for guests at a big party where mistakes matter. Testnets are like practicing in your kitchen with fake ingredients so you can perfect the recipe without wasting real food.

┌───────────────┐       ┌───────────────┐
│   Mainnet     │       │   Testnets    │
│ (Real Money)  │       │ (Fake Money)  │
└──────┬────────┘       └──────┬────────┘
       │                       │
       │                       │
       ▼                       ▼
┌───────────────┐       ┌───────────────┐
│ Real Transactions│     │ Testing & Dev │
│ & Smart Contracts│     │ Smart Contracts│
└─────────────────┘     └───────────────┘

Build-Up - 6 Steps

1

Foundation

What is Ethereum mainnet?

Concept: Introduce the main Ethereum network where real transactions happen.

The Ethereum mainnet is the live blockchain where real Ether (ETH) is used. People send real money, deploy smart contracts, and interact with decentralized apps here. It is the official network that secures and records all real Ethereum activity.

Result

Learners understand that mainnet is the real Ethereum network with real value.

Knowing mainnet is the real network helps learners appreciate why safety and security are critical.

2

Foundation

What are Ethereum testnets?

Concept: Explain testnets as separate networks for safe testing.

Testnets are copies of the Ethereum network but use fake Ether. Developers use testnets to try out smart contracts and apps without risking real money. Popular testnets include Goerli and Sepolia. They behave like mainnet but are isolated and safe.

Result

Learners see testnets as safe spaces for development and experimentation.

Understanding testnets prevents costly mistakes on the mainnet by allowing safe practice.

3

Intermediate

Differences between mainnet and testnets

🤔Before reading on: Do you think testnets have the same security and value as mainnet? Commit to your answer.

Concept: Highlight key differences in value, security, and purpose.

Mainnet uses real Ether with real economic value and high security. Testnets use fake Ether with no real value and lower security guarantees. Testnets reset or change often, while mainnet is stable and permanent. Testnets help catch bugs before mainnet deployment.

Result

Learners can distinguish mainnet and testnets by their value and security levels.

Knowing these differences helps developers choose the right network for their task.

4

Intermediate

How to switch networks in tools

🤔Before reading on: Do you think switching networks in wallets is automatic or manual? Commit to your answer.

Concept: Teach how users and developers switch between networks in wallets and tools.

Wallets like MetaMask let you choose which Ethereum network to connect to. You can switch from mainnet to testnets like Goerli manually. This changes which blockchain your transactions go to and which Ether you use (real or fake). Developers use this to test before going live.

Result

Learners know how to change networks in common Ethereum tools.

Understanding network switching is essential for safe development and testing.

5

Advanced

Deploying smart contracts on testnets

🤔Before reading on: Do you think deploying on testnet costs real Ether or free? Commit to your answer.

Concept: Explain the process and cost of deploying contracts on testnets.

Deploying smart contracts on testnets requires fake Ether, which you can get from faucets for free. This lets you test contract behavior and interactions without spending real money. Once tested, you deploy on mainnet with real Ether. This step reduces bugs and risks.

Result

Learners understand deployment costs and procedures on testnets.

Knowing deployment on testnets is free and safe encourages thorough testing.

6

Expert

Network forks and testnet resets

🤔Before reading on: Do you think testnets keep all history forever like mainnet? Commit to your answer.

Concept: Discuss how testnets can reset or fork, unlike mainnet.

Testnets often reset their blockchain history or fork to new versions to test upgrades or fix issues. This means testnet data is temporary and can disappear. Mainnet keeps all history permanently. Developers must be aware that testnet data is not guaranteed to last.

Result

Learners grasp the temporary and experimental nature of testnets.

Understanding testnet resets prevents confusion and data loss during development.

Under the Hood

Ethereum networks run independent blockchains with their own nodes and consensus. Mainnet nodes validate real transactions and secure the network with economic incentives. Testnet nodes run similar software but use test Ether and allow more flexible rules for experimentation. Each network has its own chain ID to prevent cross-network confusion.

Why designed this way?

Ethereum was designed with separate networks to protect the mainnet from bugs and attacks during development. Testnets provide a playground for innovation without risking real assets. This separation balances security with flexibility, allowing the ecosystem to grow safely.

┌───────────────┐       ┌───────────────┐
│   Mainnet     │       │   Testnet     │
│  (Chain ID 1) │       │  (Chain ID X) │
├───────────────┤       ├───────────────┤
│ Nodes validate│       │ Nodes validate│
│ real txns     │       │ test txns     │
│ with real ETH │       │ with fake ETH │
└──────┬────────┘       └──────┬────────┘
       │                       │
       ▼                       ▼
  Real blockchain         Experimental blockchain

Myth Busters - 4 Common Misconceptions

Quick: Do you think testnet Ether has real monetary value? Commit to yes or no.

Common Belief: Testnet Ether is just like real Ether and can be used for purchases.

Reality: Testnet Ether has no real value and cannot be used outside the testnet environment.

Why it matters: Believing testnet Ether is real can lead to financial loss or confusion when trying to use it on mainnet.

Quick: Do you think transactions on testnets are as secure as on mainnet? Commit to yes or no.

Common Belief: Testnet transactions are just as secure and permanent as mainnet transactions.

Reality: Testnet transactions are less secure and can be reversed or lost due to resets or forks.

Why it matters: Assuming testnet transactions are permanent can cause developers to trust test data that might disappear.

Quick: Do you think switching networks in a wallet happens automatically based on the app? Commit to yes or no.

Common Belief: Wallets automatically switch networks depending on the app you use.

Reality: Users must manually select the network in their wallet; apps cannot force network changes automatically.

Why it matters: Not knowing this can cause failed transactions or confusion when interacting with different networks.

Quick: Do you think all testnets behave the same way and have the same rules? Commit to yes or no.

Common Belief: All Ethereum testnets are identical and interchangeable.

Reality: Different testnets have different rules, consensus mechanisms, and lifespans.

Why it matters: Using the wrong testnet can cause unexpected behavior or wasted effort in development.

Expert Zone

1

Some testnets use proof-of-authority consensus to speed up testing, which is very different from mainnet's proof-of-stake.

2

Chain IDs prevent replay attacks by ensuring transactions from one network cannot be used on another.

3

Testnets often have different gas price dynamics, so performance testing on testnets may not reflect mainnet behavior.

When NOT to use

Avoid using testnets for performance benchmarking of live apps because their network conditions differ from mainnet. For private testing, consider local blockchain simulators like Hardhat or Ganache instead of public testnets.

Production Patterns

Developers deploy contracts first on testnets like Goerli to catch bugs, then migrate to mainnet. Continuous integration pipelines often include automated tests on testnets. Some projects maintain their own private testnets for controlled testing.

Connections

Software Development Environments

Builds-on

Ethereum testnets are like development and staging environments in software, allowing safe testing before production release.

Financial Risk Management

Same pattern

Separating testnets from mainnet mirrors risk management in finance, where simulations prevent costly real-world mistakes.

Scientific Experimentation

Builds-on

Using testnets is like running controlled experiments before applying findings in real-world scenarios.

Common Pitfalls

#1 Trying to buy something with testnet Ether.

Wrong approach:

Send testnet Ether to a real exchange or merchant expecting real value.

Correct approach:

Use mainnet Ether for real purchases; testnet Ether is only for testing within testnet environments.

Root cause:

Misunderstanding that testnet Ether has no real monetary value.

#2 Deploying smart contracts directly on mainnet without testing.

Wrong approach:

Deploy contract on mainnet first to save time.

Correct approach:

Deploy and test contracts thoroughly on testnets before mainnet deployment.

Root cause:

Underestimating risks and costs of bugs on mainnet.

#3 Assuming wallet network switches automatically.

Wrong approach:

Use MetaMask without manually selecting the correct network for your app.

Correct approach:

Manually select the appropriate network in your wallet before interacting with contracts.

Root cause:

Not knowing network selection is a manual user action.

Key Takeaways

Ethereum mainnet is the real network where actual value and transactions happen.

Testnets are separate networks with fake Ether used for safe development and testing.

Switching networks in wallets is a manual process that changes which blockchain you interact with.

Testnets can reset or fork, so their data is temporary and less secure than mainnet.

Using testnets prevents costly mistakes and keeps the mainnet stable and secure.

Practice

1. Which Ethereum network should you use to test your smart contracts without risking real money?

easy

A. Private network

B. Mainnet

C. Testnet

D. Production network

Solution

1. Step 1: Understand the purpose of testnets

   Testnets are designed for testing and development without real value at risk.

2. Step 2: Compare with mainnet

   Mainnet is the live network where real transactions and value exist, so testing there risks real money.

3. Final Answer:

   Testnet -> Option C

4. Quick Check:

   Testnet = Safe testing network [OK]

Hint: Testnets are for safe practice, mainnet is for real use [OK]

Common Mistakes:

• Confusing mainnet with testnet
• Thinking private network is the default test environment
• Assuming production network is safe for testing

2. Which of the following is the correct way to specify the Ethereum mainnet network ID in your configuration?

easy

A. "networkId": 1

B. "networkId": 3

C. "networkId": 42

D. "networkId": 4

Solution

1. Step 1: Recall Ethereum network IDs

   Mainnet uses network ID 1, testnets have other IDs like 3 (Ropsten), 4 (Rinkeby), 42 (Kovan).

2. Step 2: Match the ID to mainnet

   Network ID 1 corresponds to the Ethereum mainnet.

3. Final Answer:

   "networkId": 1 -> Option A

4. Quick Check:

   Mainnet networkId = 1 [OK]

Hint: Mainnet always uses network ID 1 [OK]

Common Mistakes:

• Using testnet IDs for mainnet
• Confusing networkId with chainId
• Assuming networkId 0 is valid

3. Given the following code snippet to connect to an Ethereum network, what network will it connect to?

const provider = new ethers.providers.JsonRpcProvider("https://rinkeby.infura.io/v3/YOUR_PROJECT_ID");
const network = await provider.getNetwork();
console.log(network.name);

medium

A. "mainnet"

B. "rinkeby"

C. "ropsten"

D. "kovan"

Solution

1. Step 1: Identify the RPC URL

   The URL contains "rinkeby.infura.io", indicating the Rinkeby testnet.

2. Step 2: Understand provider.getNetwork()

   This method returns the network info based on the RPC URL, so it will return "rinkeby".

3. Final Answer:

   "rinkeby" -> Option B

4. Quick Check:

   RPC URL domain = rinkeby [OK]

Hint: Check the RPC URL domain for network name [OK]

Common Mistakes:

• Assuming default is mainnet
• Confusing testnet names
• Ignoring the URL and guessing

4. You wrote this code to deploy a contract on Ropsten testnet but get an error:

const provider = new ethers.providers.JsonRpcProvider("https://mainnet.infura.io/v3/YOUR_PROJECT_ID");
const signer = provider.getSigner();
// deploy contract code here

What is the main issue?

medium

A. Incorrect contract deployment syntax

B. Provider does not support getSigner()

C. Using mainnet RPC URL instead of Ropsten testnet URL

D. Missing private key for signer

Solution

1. Step 1: Examine the signer line

   JsonRpcProvider.getSigner() fails because public RPC providers like Infura do not expose signing accounts or private keys.

2. Step 2: Correct approach for deployment

   Create a wallet signer: const wallet = new ethers.Wallet('0x-your-private-key', provider); const signer = wallet.connect(provider);

3. Final Answer:

   Missing private key for signer -> Option D

4. Quick Check:

   Use Wallet(privateKey, provider) for signing [OK]

Hint: Use ethers.Wallet(privateKey, provider) for signing deployments [OK]

Common Mistakes:

• Using provider.getSigner() without wallet
• Assuming getSigner() works without wallet
• Overlooking private key requirement

5. You want to write a script that deploys a smart contract first on the Goerli testnet and then on the mainnet only if tests pass. Which approach correctly handles this?

hard

A. Deploy on Goerli testnet, run tests, then deploy on mainnet if tests pass

B. Deploy on mainnet first, then test on Goerli

C. Deploy simultaneously on both networks

D. Deploy only on mainnet and skip testnet

Solution

1. Step 1: Understand deployment best practices

   Testnets like Goerli are used to test contracts safely before mainnet deployment.

2. Step 2: Apply conditional deployment logic

   Deploy on Goerli, run tests, and only deploy on mainnet if tests succeed to avoid costly errors.

3. Final Answer:

   Deploy on Goerli testnet, run tests, then deploy on mainnet if tests pass -> Option A

4. Quick Check:

   Test on testnet before mainnet deployment [OK]

Hint: Test on Goerli first, then deploy mainnet if tests pass [OK]

Common Mistakes:

• Deploying on mainnet before testing
• Skipping testnets entirely
• Deploying on both networks at once