Ethereum Mainnet

What Is Ethereum Mainnet?

Ethereum Mainnet is the primary public production blockchain of the Ethereum network.

It is the live network where ETH and other crypto assets have real economic value and where confirmed transactions create lasting changes to blockchain state.

Users can send ETH, transfer tokens, interact with smart contracts, create digital assets, stake ETH, and use decentralized applications on Ethereum Mainnet.

Developers deploy production smart contracts to Mainnet after testing their code on local networks or public testnets.

The official Ethereum networks documentation describes Mainnet as the primary public Ethereum production blockchain where transactions involving actual value occur.

There is only one Ethereum Mainnet, although many independent networks use Ethereum software, Ethereum-style addresses, or the Ethereum Virtual Machine.

These other networks do not share Mainnet’s balances, transaction history, validators, smart contract state, or economic security unless a separate bridge or protocol connects them.

Ethereum Mainnet is commonly called Ethereum, Mainnet, Ethereum Layer 1, or Ethereum L1 when the context is clear.

Why Is It Called Mainnet?

The word Mainnet is short for main network.

It separates the live production blockchain from test networks, private networks, local development chains, and simulations.

Transactions on Mainnet use real ETH for gas and can move assets with real market value.

Transactions on a testnet normally use test assets that are intended only for development.

EIP-2228 standardized Ethereum Mainnet as the proper name for the Ethereum network with network ID 1 and chain ID 1.

Using the correct name helps wallets, developers, infrastructure operators, and users distinguish this network from other Ethereum-based environments.

When Did Ethereum Mainnet Launch?

Ethereum Mainnet launched on July 30, 2015, when its genesis block went live under the Frontier release.

A genesis block is the first block in a blockchain’s history.

Every later Ethereum Mainnet block can be traced back through cryptographic links to this starting point.

The official Ethereum ten-year history identifies July 30, 2015 as the date on which Ethereum’s genesis block launched the network.

Mainnet has changed through many protocol upgrades since its launch, but its accounts, balances, contracts, and block history have continued as one evolving blockchain.

An Ethereum upgrade changes the rules followed by participating software rather than creating a replacement token that users must purchase.

What Is the Ethereum Mainnet Chain ID?

Ethereum Mainnet uses chain ID 1.

The hexadecimal form returned by the eth_chainId JSON-RPC method is 0x1.

A chain ID identifies the blockchain for transaction signing and helps protect transactions from being replayed on a different network.

EIP-155 lists chain ID 1 as Ethereum Mainnet and introduced chain-aware replay protection for signed transactions.

Wallets and decentralized applications should verify the chain ID before requesting a signature or sending a transaction.

An application displaying Ethereum-style addresses does not prove that it is connected to Ethereum Mainnet.

The network name, chain ID, RPC endpoint, and expected contract addresses should all be checked.

Chain ID vs. Network ID

Ethereum Mainnet commonly uses both chain ID 1 and network ID 1, but these values serve different purposes.

The chain ID is used in transaction signatures and other chain-specific authorization systems.

The network ID has traditionally been used during peer-to-peer network communication and network identification.

Modern wallets and decentralized applications usually focus more heavily on chain ID because it directly affects transaction signing and replay protection.

The official Ethereum JSON-RPC documentation explains how software can retrieve the configured chain ID and network ID from a node.

How Ethereum Mainnet Works

Ethereum Mainnet is maintained by independent computers running compatible Ethereum client software.

These computers communicate through a peer-to-peer network and independently verify blocks, transactions, smart contract execution, and consensus messages.

Users create transactions through wallets or applications and sign them with the appropriate account credentials.

Transactions are broadcast to Ethereum nodes and can enter public or private transaction-routing systems.

A selected validator proposes a block containing an ordered collection of transactions.

Other validators verify the block and submit attestations supporting the chain they consider valid.

Execution clients process the transactions and calculate the resulting account balances, contract storage, logs, receipts, and other state changes.

Consensus clients process validator votes, fork choice, justification, and finality.

Each honest node applies the same protocol rules so that it can reject invalid transactions or blocks without trusting a central server.

Ethereum’s Execution and Consensus Layers

Ethereum Mainnet combines an execution layer with a consensus layer.

The execution layer manages transactions, accounts, smart contract bytecode, the Ethereum Virtual Machine, gas, and blockchain state.

The consensus layer manages validators, attestations, block proposals, fork choice, rewards, penalties, and finality.

A full Ethereum node normally runs one execution client and one consensus client.

A validating node also runs validator software that uses signing keys to perform assigned consensus duties.

The official Ethereum nodes and clients guide explains how these components communicate while performing different jobs.

Neither layer is sufficient by itself to operate the current Ethereum Mainnet.

Ethereum Mainnet and Proof-of-Stake

Ethereum Mainnet currently uses proof-of-stake consensus.

Validators commit ETH as economic collateral and run software that participates in block production and confirmation.

Correct participation can earn protocol rewards, while downtime creates penalties and provably conflicting behavior can cause slashing.

The official Ethereum proof-of-stake documentation explains how validators are selected to propose blocks and attest to the network’s state.

Ethereum originally used proof-of-work mining.

The Merge permanently replaced Ethereum Mainnet’s proof-of-work system with proof-of-stake on September 15, 2022.

The transition preserved Ethereum’s existing accounts, smart contracts, balances, and transaction history.

Users did not need to exchange an old version of ETH for a new version.

Validators on Ethereum Mainnet

A validator is a protocol participant that has deposited ETH and entered Ethereum’s active validator set.

Validators are assigned duties according to the consensus protocol.

Most validators regularly submit attestations expressing their view of the chain head and finalized checkpoints.

A validator is occasionally selected to propose a new block.

Validators can also receive sync committee assignments that help light clients follow Ethereum.

A native validator needs an effective balance of at least 32 ETH to activate.

Following Pectra, an eligible compounding validator can have an effective balance as high as 2,048 ETH.

Running an ordinary non-validating Ethereum node does not require staking 32 ETH.

Anyone can run a node to verify Ethereum data independently without becoming a block proposer.

Blocks, Slots, and Epochs

Ethereum proof-of-stake organizes time into slots and epochs.

A slot lasts approximately 12 seconds and provides one opportunity for a validator to propose a block.

A slot can remain empty when no valid block is proposed or accepted in time.

An epoch contains 32 slots and lasts approximately 6.4 minutes.

Validators receive duties and participate in checkpoint voting across these time periods.

The official Ethereum block documentation explains how blocks group transactions and connect the network’s state history.

A block number counts accepted execution blocks, while a slot counts consensus-layer time opportunities.

These values should not be treated as interchangeable because an empty slot does not create a new execution block.

Transaction Inclusion vs. Finality

A transaction becomes included when it appears in a block accepted near the head of the chain.

Inclusion provides useful evidence that the transaction has executed, but a recently included block can still face limited reorganization risk.

A blockchain reorganization replaces one recent chain branch with another branch selected by the protocol’s fork-choice rules.

Finality provides much stronger confidence that a block will remain permanently in the accepted history.

Ethereum normally finalizes checkpoints after sufficient validator participation across multiple epochs.

Under ordinary conditions, finality takes approximately 13 to 15 minutes rather than one 12-second slot.

The official Ethereum finality documentation explains that reverting finalized blocks would require a critical consensus failure and the destruction of at least one-third of total staked ETH.

A wallet may show a transaction as confirmed before the containing block is finalized.

Applications should choose a confirmation policy appropriate to the value and risk of the transaction.

The Ethereum Virtual Machine on Mainnet

The Ethereum Virtual Machine, or EVM, is the execution environment that runs Mainnet smart contract bytecode.

Every honest execution client should calculate the same state transition from the same starting state and ordered transaction data.

The EVM performs arithmetic, reads transaction input, accesses memory, updates contract storage, creates event logs, transfers value, and calls other contracts.

The official Ethereum Virtual Machine documentation describes the EVM as a decentralized environment that executes code consistently across Ethereum nodes.

Gas limits the amount of computational work that one transaction can request.

A valid smart contract can still contain unsafe, dishonest, or financially harmful logic.

The EVM checks execution rules rather than deciding whether a contract is a good product or a safe investment.

Ethereum Mainnet State

Ethereum state is the current collection of account information recognized by the network.

It includes ETH balances, account nonces, smart contract code, and contract storage.

Each valid transaction changes this state according to protocol and smart contract rules.

A token balance is usually stored inside a token contract rather than as a native field in the user’s Ethereum account.

A decentralized finance position may be represented across several contracts and storage locations.

Ethereum nodes calculate a new state root after processing a block.

This cryptographic commitment allows nodes to verify that they reached the same resulting state.

Accounts on Ethereum Mainnet

Ethereum Mainnet includes externally owned accounts and contract accounts.

An externally owned account is traditionally controlled by a private key or a more advanced wallet authorization system.

A contract account contains EVM bytecode and executes that code when it receives a valid call.

Both account types use 20-byte Ethereum addresses.

The same private key normally produces the same address on several EVM networks, but balances and activity remain separate on each chain.

An address holding assets on Ethereum Mainnet does not automatically hold the same assets on a testnet or another EVM network.

Users must verify the selected chain before reading a balance or signing a transaction.

ETH on Ethereum Mainnet

Ether, commonly identified by the symbol ETH, is Ethereum Mainnet’s native crypto asset.

ETH is used to pay transaction fees, provide validator stake, transfer value, and serve as an asset within supported smart contracts.

ETH is native to Ethereum’s protocol and is not implemented as an ordinary ERC-20 token contract.

A tokenized representation of ETH is a separate smart contract asset designed for easier use with token interfaces.

The official Ethereum guide to ETH explains its role in paying for network activity and securing proof-of-stake consensus.

ETH’s market price can rise or fall independently from Ethereum Mainnet’s technical operation.

Holding ETH does not give a user ownership of the Ethereum network or guaranteed control over protocol development.

Transactions on Ethereum Mainnet

An Ethereum transaction is a cryptographically authorized instruction submitted to the network.

A transaction can transfer ETH, deploy a contract, call a contract function, or authorize supported account behavior.

Common transaction fields include the sender, destination, value, nonce, gas limit, fee settings, chain ID, input data, and signature.

The nonce orders transactions submitted by the same externally owned account and helps prevent accidental replay.

A transaction is not complete merely because a wallet generated a transaction hash.

It must be broadcast, included in a valid block, and executed successfully.

The official Ethereum transaction documentation explains current transaction structures and their role in changing state.

Successful and Failed Mainnet Transactions

A successful transaction completed its top-level execution without reverting.

This status does not guarantee that the user received a fair trade, selected the correct address, or interacted with a safe contract.

A failed transaction did not preserve its intended state changes.

The sender normally still pays for the gas consumed before the failure.

Common failure causes include insufficient gas, contract reverts, expired trade conditions, missing token approval, inadequate balances, or incorrect function parameters.

Confirmed Ethereum Mainnet transactions are generally irreversible.

A new correcting transaction may be possible when the asset controller or contract rules allow it, but the original transaction cannot simply be deleted.

Gas on Ethereum Mainnet

Gas measures the computational and storage resources consumed by Ethereum Mainnet transactions.

Each EVM operation has a gas cost based on the resources it requires.

A simple ETH transfer normally consumes less gas than a complex smart contract transaction.

The transaction’s gas limit sets the maximum gas available to execution.

The sender pays according to the gas actually consumed and the effective price paid per gas unit.

The official Ethereum gas documentation explains gas limits, base fees, priority fees, and transaction cost calculation.

A high gas limit does not mean the entire limit will necessarily be spent.

A gas limit that is too low can cause execution to stop and revert.

Base Fees and Priority Fees

Every Ethereum Mainnet block has a base fee that acts as the minimum protocol price for including normal execution gas.

The base fee changes automatically according to recent demand for block capacity.

The base fee paid by a transaction is burned and removed from the circulating ETH supply.

A priority fee provides additional compensation to the block proposer.

A transaction can also specify a maximum total fee it is willing to pay.

The unused difference between the maximum and actual required fee is not automatically paid in full to the proposer.

Fee settings affect how attractive a transaction is for inclusion but cannot guarantee a particular execution result.

Smart Contracts on Ethereum Mainnet

A smart contract is a program deployed to an Ethereum Mainnet address.

Smart contracts can create tokens, manage digital ownership, hold collateral, process swaps, distribute rewards, enforce governance rules, or coordinate other on-chain actions.

Contract code executes according to the transaction input and current blockchain state.

A deployed contract can call other contracts during the same atomic transaction.

This composability allows applications to build on shared on-chain standards and services.

It also allows a weakness in one dependency to affect other connected applications.

Users should verify contract addresses, permissions, upgrade controls, and transaction details before granting access to valuable assets.

Tokens on Ethereum Mainnet

Most tokens on Ethereum Mainnet are implemented through smart contracts.

ERC-20 defines a common interface for fungible tokens.

ERC-721 and ERC-1155 support common interfaces for unique and multi-token assets.

The official Ethereum token standards documentation explains how shared interfaces improve interoperability between contracts, wallets, and applications.

Anyone can deploy a token contract using a familiar name or symbol.

A token symbol does not uniquely identify an asset.

The Mainnet contract address should be verified through an authoritative project or issuer source.

A token with the same branding on another chain is a separate asset unless a defined bridge or issuer relationship connects it.

Event Logs and Transaction Receipts

Smart contracts can emit event logs while transactions execute.

Wallets, block explorers, and data services use these logs to identify token transfers, approvals, swaps, deposits, votes, and other contract actions.

Logs are included in transaction receipts after successful execution.

A receipt also records execution status, gas use, block information, and other transaction results.

Event logs are designed mainly for off-chain applications and cannot be searched directly by ordinary smart contract code.

A familiar event name does not prove that the emitting contract is legitimate because any contract can emit a similar event.

Ethereum Mainnet vs. a Testnet

Ethereum Mainnet is the live production network, while a testnet is intended for development and testing.

Mainnet ETH has real market value and pays for production transactions.

Testnet ETH is intended to support testing and should not be promoted as an investment asset.

Testnets use different chain IDs, validators, blocks, balances, and contract deployments.

A contract that works on a testnet may still fail or become unsafe on Mainnet because of different liquidity, gas, state, permissions, or adversarial conditions.

Developers should test thoroughly before deploying code that can control real assets.

A testnet contract address should never be assumed to identify the same contract on Mainnet.

Ethereum Mainnet vs. a Local Network

A local Ethereum network runs on a developer’s own computer or controlled environment.

It allows rapid testing without depending on public validators or spending real ETH.

Developers can reset a local chain, create funded test accounts, control block production, and inspect execution closely.

Ethereum Mainnet cannot be reset by an application developer when a test fails.

Local success does not prove Mainnet readiness because real network state, fee competition, liquidity, transaction ordering, and hostile users may produce different results.

Ethereum Mainnet vs. a Private Ethereum Network

A private Ethereum network uses related software but limits participation to a controlled set of nodes or organizations.

It can use a different genesis block, chain ID, consensus configuration, and account state.

Private networks do not inherit Ethereum Mainnet’s validator set, public liquidity, transaction history, or economic security.

The word private may describe restricted network participation rather than confidential transaction data.

Users should not assume that a private Ethereum-based network provides the same censorship resistance or neutrality as public Mainnet.

Ethereum Mainnet and Layer 2 Networks

A Layer 2 network processes transactions outside Ethereum Mainnet’s main execution environment while using Ethereum for part of its settlement, data availability, or security model.

Rollups execute or organize transactions separately and publish data or cryptographic commitments to Mainnet.

This design can provide lower user fees and greater transaction capacity.

The official Ethereum Layer 2 guide explains how rollups extend Ethereum while using it as a settlement base.

A transaction confirmed by a Layer 2 sequencer is not the same as a transaction executed directly on Ethereum Mainnet.

Bridges, proof systems, data publication, upgrade controls, and withdrawal procedures create additional risks.

Users should verify which chain holds their assets and which security assumptions apply.

Blobs and Layer 2 Data

Ethereum Mainnet supports blobs as a lower-cost data channel designed mainly for rollups.

Blob data has a separate fee market from ordinary EVM execution gas.

Dencun introduced blobs through EIP-4844 on March 13, 2024.

Pectra later increased blob capacity.

Fusaka introduced Peer Data Availability Sampling, commonly called PeerDAS, allowing validators to sample portions of blob data rather than requiring every node to download every complete blob.

The official Fusaka documentation explains how PeerDAS supports safer growth in rollup data capacity.

Blobs are temporary consensus data and are not a permanent general-purpose storage system for ordinary applications.

What Was Pectra?

Pectra was a major Ethereum Mainnet upgrade activated on May 7, 2025.

Its name combined Prague, the execution-layer upgrade, with Electra, the consensus-layer upgrade.

Pectra introduced account improvements through EIP-7702, increased blob capacity, improved validator deposit handling, and expanded the maximum effective balance of compounding validators to 2,048 ETH.

It also enabled execution-layer-triggered validator withdrawal and exit requests.

The official Pectra upgrade page documents its Mainnet activation and included improvements.

A wallet or application must deliberately support new transaction and account features before users can benefit from them safely.

What Was Fusaka?

Fusaka is the latest completed major Ethereum Mainnet upgrade as of July 16, 2026.

It activated on December 3, 2025.

Its name combines Fulu for the consensus-layer upgrade and Osaka for the execution-layer upgrade.

Fusaka’s main scaling feature was PeerDAS, which improved the way nodes verify the availability of blob data.

Fusaka also included changes supporting higher Layer 1 capacity, more predictable resource limits, and future parallel execution work.

EIP-7825 introduced a per-transaction gas cap of 2²⁴ gas, which is approximately 16.78 million gas.

Later Blob Parameter Only updates gradually increased blob capacity without requiring another complete upgrade bundle.

Fusaka standardized a 60 million default block gas limit through EIP-7935, although Ethereum’s gas-limit mechanism still involves validator coordination.

What Comes After Fusaka?

Glamsterdam is the next major Ethereum upgrade currently planned for the second half of 2026.

It is still in development and is not part of Ethereum Mainnet’s active rules as of July 16, 2026.

Its proposed areas include further scaling, improved block construction, resource accounting, and groundwork for more parallel execution.

The official Glamsterdam roadmap page provides the latest public status.

Planned contents and activation timing can change during research, specification, implementation, and testing.

Applications should not rely on a proposed feature until the upgrade has been finalized, implemented in supported clients, and activated on Mainnet.

How Ethereum Mainnet Upgrades

Ethereum has no single company that can privately update every node.

Protocol changes are discussed publicly through research forums, Ethereum Improvement Proposals, developer calls, client teams, security reviews, and testing programs.

An accepted change must be implemented by client software and coordinated for activation at a defined Mainnet time, block, slot, or epoch.

Node operators must install compatible software before the activation point.

Nodes following incompatible rules may separate from the accepted network.

The official Ethereum roadmap explains that upgrade priorities and schedules can change as research and network needs evolve.

A roadmap is a development direction rather than a guaranteed release calendar.

Hard Forks on Ethereum Mainnet

A hard fork is a protocol rule change that is not backward compatible with older rules.

Ethereum commonly uses coordinated hard forks to activate planned network upgrades.

When the community, client teams, node operators, infrastructure providers, and validators broadly adopt the new rules, the upgraded chain normally continues as Ethereum Mainnet.

A contentious split can produce two independent chains when meaningful groups continue following different rules.

After a split, the chains can have similar earlier history but separate future blocks, assets, prices, and security conditions.

Users should verify the chain ID, supported client rules, and recognized network before signing transactions around major upgrades.

Ethereum Mainnet Security

Ethereum Mainnet security comes from protocol rules, cryptography, distributed verification, proof-of-stake economics, client diversity, and widespread node operation.

Validators risk penalties and slashing when they violate specified consensus rules.

Independent nodes verify blocks instead of accepting them solely because a powerful participant proposed them.

Finality makes deeply confirmed history expensive to reverse.

Ethereum can still face software bugs, network disruptions, validator concentration, censorship pressure, smart contract exploits, or user key theft.

Mainnet security does not make every application deployed on Mainnet secure.

A smart contract can fail even while Ethereum itself continues operating correctly.

Client Diversity

Ethereum Mainnet is implemented by several independent execution and consensus client teams.

Client diversity reduces dependence on one software codebase.

A serious bug in a dominant client can affect a large part of the network at the same time.

Independent implementations can identify differences through testing and real-world operation.

Every compatible client must still follow the same active Mainnet rules and calculate the same valid results.

Validator operators should monitor client releases and update before scheduled network upgrades.

Running an Ethereum Mainnet Node

Running a node allows a user or organization to verify Ethereum Mainnet directly.

A node can provide blockchain data to a wallet, application, validator, or internal service.

The operator normally runs both an execution client and a consensus client.

Operating a non-validating node does not require a 32 ETH deposit.

The official Ethereum node guide explains node setup and its benefits.

A node requires suitable storage, memory, processing capacity, bandwidth, maintenance, and software updates.

Running a personal node can reduce dependence on a remote RPC provider, although it creates additional technical responsibility.

RPC Access to Ethereum Mainnet

Wallets and decentralized applications commonly access Ethereum Mainnet through JSON-RPC.

RPC methods can retrieve balances, blocks, receipts, logs, fee data, contract state, and transaction information.

They can also broadcast signed transactions.

A remote RPC service can observe requests, return stale data, impose rate limits, experience outages, or apply its own access policies.

High-value applications may compare several independent sources or operate their own node.

An RPC endpoint does not hold the user’s assets unless a separate custody arrangement exists.

The signed transaction remains authorized by the user’s wallet or signing system.

Bridges to and From Ethereum Mainnet

A bridge transfers or represents assets and messages between Ethereum Mainnet and another blockchain environment.

A bridge may lock assets on Mainnet and create a corresponding representation elsewhere.

Another design may burn tokens on one network and authorize minting on another.

Bridges add smart contract, proof, validator, custodian, relayer, liquidity, and upgrade risks.

A bridged token is not automatically identical to a natively issued Mainnet asset.

Users should verify the bridge, source chain, destination chain, token contract, expected received asset, and withdrawal process.

Ethereum Mainnet’s security cannot protect every independent bridge component from failure.

Mainnet Assets vs. Assets on Other Networks

An asset exists within the state of a specific blockchain or contract system.

ETH on Ethereum Mainnet is different from a token representation of ETH on another network.

A stablecoin issued through one Mainnet contract may differ legally and technically from a token with the same symbol elsewhere.

The same wallet address can display different assets depending on the selected network.

Sending an asset through an unsupported network can make it difficult or impossible for the intended service to credit the transfer.

Users should verify the network and contract rather than relying only on the asset name.

How to Select Ethereum Mainnet in a Wallet

A wallet’s network selector should identify Ethereum Mainnet and chain ID 1.

The native currency should be ETH.

The wallet should connect through a trusted Mainnet RPC endpoint.

Users should verify the complete destination address, asset, amount, gas estimate, and contract interaction before signing.

A website can request that a wallet switch networks, but the user should inspect the request rather than approving it automatically.

Adding a custom network with misleading information does not turn that network into Ethereum Mainnet.

The returned chain ID is a stronger technical identifier than the displayed network name alone.

How to Verify a Mainnet Transaction

The first step is to obtain the complete transaction hash from the sending wallet or application.

The second step is to check the transaction through a trusted Ethereum Mainnet node or block explorer.

The third step is to confirm chain ID 1 and the correct network context.

The fourth step is to check whether the transaction is pending, successful, or failed.

The fifth step is to verify the sender, destination, transferred value, token contract, and event logs.

The sixth step is to review the block number and confirmation level.

The seventh step is to wait for stronger confirmation or finality when the economic value requires it.

A screenshot should not be treated as final proof because screenshots can be altered.

Example of an Ethereum Mainnet Transaction

Suppose a user wants to transfer 0.5 ETH to another Mainnet address.

The wallet confirms that it is connected to chain ID 1.

It creates a transaction containing the recipient address, 0.5 ETH value, nonce, gas limit, fee settings, and chain ID.

The user reviews the details and signs the transaction.

The wallet broadcasts the signed data through an Ethereum Mainnet RPC connection.

A validator includes the transaction in a proposed block.

Execution clients verify the signature, nonce, available balance, gas, and state transition.

The sender’s balance is reduced by the transferred value and transaction fee.

The recipient’s balance increases by 0.5 ETH.

The transaction receipt records its status and gas use.

Later validator votes provide stronger confidence until the containing checkpoint becomes finalized.

Common Misunderstandings About Ethereum Mainnet

One common misunderstanding is that Ethereum Mainnet is operated by one company.

It is maintained through open protocol rules and independently operated software.

Another misunderstanding is that every EVM network is part of Ethereum Mainnet.

Independent chains can use the EVM while maintaining separate state and security.

A third misunderstanding is that the same wallet address holds the same assets on every network.

Balances and contracts are chain specific.

A fourth misunderstanding is that a successful Mainnet transaction must be safe or profitable.

Ethereum can correctly execute a harmful transaction authorized by the user.

A fifth misunderstanding is that running a node requires 32 ETH.

Only validator activation requires the native staking deposit.

A sixth misunderstanding is that a testnet asset will become valuable when transferred to Mainnet.

Testnet and Mainnet assets exist in separate blockchain states.

A seventh misunderstanding is that every Layer 2 transaction executes directly on Mainnet.

Layer 2 systems process activity separately and use Mainnet through their own settlement and data mechanisms.

FAQ

What is Ethereum Mainnet?

Ethereum Mainnet is the primary public production Ethereum blockchain where ETH, tokens, smart contracts, and transactions carry real economic value.

What is the Ethereum Mainnet chain ID?

Ethereum Mainnet uses chain ID 1, which is returned in hexadecimal form as 0x1.

When did Ethereum Mainnet launch?

Ethereum Mainnet launched on July 30, 2015 with the Frontier genesis block.

Is Ethereum Mainnet the same as Ethereum?

Ethereum Mainnet is the live production blockchain commonly meant when people refer to Ethereum, although Ethereum can also describe the wider protocol and ecosystem.

Does Ethereum Mainnet still use mining?

No, Ethereum Mainnet permanently replaced proof-of-work mining with proof-of-stake on September 15, 2022.

What is the native asset of Ethereum Mainnet?

ETH is Ethereum Mainnet’s native asset and is used for transaction fees, staking, and value transfer.

How often does Ethereum Mainnet create blocks?

Ethereum provides a block proposal opportunity approximately every 12-second slot, although some slots can remain empty.

How long does Ethereum Mainnet finality take?

Under normal conditions, strong protocol finality usually takes approximately 13 to 15 minutes.

Can an Ethereum Mainnet transaction be reversed?

A confirmed transaction generally cannot be reversed unless the recipient or smart contract voluntarily performs a new correcting action.

Why do Mainnet transactions require gas?

Gas measures and prices the computational and storage resources used to process transactions and smart contracts.

Is Mainnet ETH the same as testnet ETH?

No, Mainnet ETH has real economic value, while testnet ETH is intended only for development and exists on a separate network.

Can the same address be used on Mainnet and another EVM chain?

The same key can produce the same address, but balances, transactions, contracts, and assets remain separate on each chain.

Are Layer 2 networks part of Ethereum Mainnet?

Layer 2 networks are separate execution environments that use Ethereum Mainnet for specified settlement, security, or data functions.

Does a smart contract deployed on Mainnet mean it is safe?

No, deployment only means the contract exists on Mainnet and does not prove that its code, permissions, or economic design are secure.

Can anyone run an Ethereum Mainnet node?

Yes, anyone with suitable hardware and internet access can run a node without staking ETH.

What was the latest Ethereum Mainnet upgrade?

As of July 16, 2026, Fusaka is the latest completed major upgrade and was activated on December 3, 2025.

Is Glamsterdam active on Ethereum Mainnet?

No, Glamsterdam is currently planned for the second half of 2026 and is not active as of July 16, 2026.

How can I confirm that my wallet is on Ethereum Mainnet?

Check that the wallet displays Ethereum Mainnet, chain ID 1, and ETH as the native gas asset.

Can Ethereum Mainnet go offline if one website fails?

No, one wallet, website, RPC endpoint, or application can fail while independently operated Ethereum nodes continue processing the network.

What is the safest way to verify a Mainnet payment?

Check the live transaction hash, chain ID, execution status, sender, recipient, asset contract, amount, and confirmation level through a trusted Mainnet data source.

Conclusion

Ethereum Mainnet is the primary public production blockchain of the Ethereum ecosystem.

It launched on July 30, 2015 and uses chain ID 1.

Mainnet records real-value ETH transfers, token activity, smart contract execution, validator operations, event logs, and application state.

Independent execution and consensus clients verify the network according to shared protocol rules.

Proof-of-stake validators propose blocks, submit attestations, and provide economic security through staked ETH.

The EVM executes smart contracts, while gas limits and prices the computational resources used by transactions.

Mainnet differs from testnets, private networks, local development chains, Layer 2 systems, and other EVM-compatible blockchains.

Addresses can look identical across these networks even though their balances, contracts, assets, and transaction histories are separate.

Pectra expanded account and validator capabilities in May 2025, while Fusaka introduced PeerDAS and further scaling improvements in December 2025.

Glamsterdam remains a future upgrade and should not be treated as an active Mainnet feature until its final activation occurs.

Users should verify chain ID 1, the correct contract address, transaction details, gas settings, and confirmation status before moving assets.

Understanding Ethereum Mainnet helps crypto users distinguish the live Ethereum blockchain from related networks and evaluate the real security, fee, finality, and smart contract risks of on-chain activity.