Blockchain Networks

Introduction

A blockchain does not exist as a single global thing: it exists as many separate networks, each running its own independent ledger, its own rules, and its own set of validators. Bitcoin, Ethereum, and dozens of others are not different "brands" of the same network; they are, structurally, completely separate systems that happen to share the same underlying idea.

This lesson looks at what actually makes a "network" in this context: how transactions are validated, why fees exist, how networks scale through layers, and how assets sometimes move between one network and another. None of this requires guessing at any asset's price or making an investment decision: it is infrastructure, and infrastructure is worth understanding on its own terms.

By the end of this lesson you will be able to explain, in plain terms, what a blockchain network is, why so many of them exist, how a transaction gets validated, what gas fees pay for, the difference between a Layer 1 and a Layer 2, and how to avoid the handful of mistakes that most often cost beginners money when moving between networks.

What Is a Blockchain Network

Strip away the branding and a blockchain network is three things working together: a set of computers (nodes) that each keep a full copy of the same ledger, a set of rules (a protocol) that every node agrees to follow, and a mechanism (consensus) that lets thousands of independent nodes agree on which transactions are valid and in what order: without any single party being in charge.

Every network you'll ever interact with, no matter its name, is some specific combination of these same three ingredients: who can run a node, what rule set they enforce, and how they reach agreement.

Why Different Blockchains Exist

If one network could do everything perfectly, there would be no reason for more than one to exist. In practice, every design choice involves a trade-off, and different networks make different trade-offs on purpose.

None of these designs is universally "better": they are answers to different questions. A network optimized for maximum decentralization will rarely also be the fastest one, and a network optimized for speed will usually concentrate validation among fewer participants.

How a Network Works

Once you understand the three ingredients above, the day-to-day operation of a network is a short, repeating cycle.

• Transaction Created: a user builds a request (e.g. "send X amount to this address") and signs it with their private key.
• Broadcast to Nodes: the signed transaction is sent out and quickly reaches many nodes across the network.
• Included in a Block: a node responsible for producing the next block picks up pending transactions and groups them together.
• Block Validated: other nodes independently check that every transaction in the block follows the rules (valid signature, sufficient balance, no duplicate spending).
• Added to the Chain: once enough nodes agree the block is valid, it is appended to the ledger, and every node updates its own copy.

This cycle repeats continuously, and the time it takes to complete varies enormously between networks: from a couple of seconds to several minutes.

Transaction Validation

"Validation" is the step that turns a raw request into something the entire network trusts. Two things need to be true before a transaction is accepted.

The exact mechanism that produces this agreement (who is allowed to propose the next block, and how disagreements are resolved) is what's usually called the network's "consensus mechanism," a topic covered from the ground up in Module 01.

Gas Fees

Producing and validating blocks costs real resources (computing power, storage, and bandwidth) and someone has to be compensated for providing them. "Gas" is the unit networks use to measure how much computational work a given transaction requires; the "gas fee" is the price paid, in the network's native token, for that work.

Fees serve a second purpose beyond payment: they make it costly to spam the network with pointless transactions. Without any fee at all, flooding a network with millions of trivial transactions would be free, and blocks would fill up with noise instead of genuine activity.

Fees rise and fall with how busy a network is at any given moment: more people trying to transact at once means more competition for the same block space, and higher fees to be included sooner. This lesson only covers what a fee represents, not how to speculate on its future cost.

Layer 1

A Layer 1 is a base network: it has its own independent ledger, its own validators, and its own consensus mechanism. It doesn't depend on any other network to record or secure its transactions; it is the foundation.

Being the foundation comes with a trade-off: because every validator has to process every transaction directly, a Layer 1 that also wants a large, geographically spread set of independent validators usually can't also process an unlimited number of transactions per second. That trade-off is explored further in the next section.

• Provides the ultimate security guarantee: everything else that builds on top of it inherits that security.
• Changes to its core rules are slow and deliberate on purpose, since they affect everyone using it.
• Transaction capacity is limited by how much every single validator can process.

Layer 2

A Layer 2 is a separate system built on top of a Layer 1 to handle transactions faster and more cheaply, while still relying on that Layer 1 to guarantee security. Rather than every transaction being processed and stored directly by the base network, a Layer 2 processes many transactions itself and periodically settles a compressed summary back down to the Layer 1.

This means a Layer 2 inherits most of the security of its underlying Layer 1 without inheriting its capacity limits: at the cost of some added complexity, and, in some designs, a short delay before a transaction is considered fully final.

Neither replaces the other: a healthy ecosystem generally uses a Layer 1 as the trust anchor and one or more Layer 2s to handle everyday volume cheaply.

EVM-Compatible Networks

The Ethereum Virtual Machine (EVM) is the standardized environment that executes smart contracts on Ethereum: a common set of instructions that every compliant node understands and runs identically. "EVM-compatible" simply means a different network chose to implement that same execution environment.

The practical benefit is portability: a smart contract, developer tool, or wallet built for one EVM-compatible network usually works on another EVM-compatible network with little or no modification, because they're speaking the same underlying language.

• Developers can reuse code and tools across multiple networks instead of learning a new environment for each one.
• Wallets that support one EVM-compatible network can typically support others by simply adding a new network configuration.
• EVM compatibility describes the execution environment only: it says nothing about a network's validators, consensus mechanism, or security assumptions, which can still differ significantly.
• The same wallet address format is shared across EVM-compatible networks, which is convenient: but, as covered in the mistakes section, is also a common source of confusion.

Bridges

Because every network keeps its own independent ledger, an asset that exists on one network doesn't natively exist on another: there is no built-in way for Network A to know anything happened on Network B. A bridge is the infrastructure that lets a user move value or information from one network to another despite this separation.

Most bridges follow one of two general patterns: locking an asset on the original network while minting a representative version on the destination network, or burning an asset on one side while releasing an equivalent that was already reserved on the other. In both cases, the user ends up with something on the destination network that represents value from the source network.

• A bridge adds a new piece of infrastructure. It introduces a new point of trust between two networks that were not designed to talk to each other.
• Bridges are a frequent target of large-scale exploits. They concentrate a lot of value in one place, which makes them attractive targets.
• A bridged asset is a representation, not the original moved physically. Its value depends on the bridge continuing to honor that representation correctly.

How to Choose a Network Correctly

There is no single "best" network: there is only the network that fits what you're actually trying to do. A short checklist helps make that decision deliberately instead of by default.

• Purpose. What are you actually using the network for? Occasional transfers, running an application, or something else can point toward different priorities.
• Fees and speed. How much does a typical transaction cost on this network, and how long does it take to be confirmed?
• Security assumptions. How many independent validators does the network have, and how long has it operated without a major incident?
• Ecosystem and tooling. Are the wallets, explorers, and applications you'll need actually well supported on this network?
• Compatibility with what you already use. Does your existing wallet support this network natively, or would you need to add a new configuration?

Common Mistakes

Nearly every network-related loss traces back to one of these avoidable mistakes.

• Sending an asset to the wrong network. The exact same address format can exist on multiple EVM-compatible networks: sending an asset intended for one network to that address on a different network can make it unrecoverable.
• Forgetting that fees are paid in the native token of that network. Having funds on a network is not the same as having enough of its native token to pay for a transaction.
• Assuming "EVM-compatible" means "identical." Compatible networks can still differ significantly in security assumptions, validator count, and maturity.
• Using a bridge without checking it first. Bridging funds through an unfamiliar or unaudited bridge concentrates risk in a single piece of infrastructure.
• Choosing a network based on hype instead of fit. The network that's trending is not automatically the one that matches your actual purpose, budget, or risk tolerance.

Summary

A blockchain network is a set of nodes, a set of rules, and a way for those nodes to agree: validated transaction by validated transaction, block by block. Different networks make different trade-offs between decentralization, security, and speed, which is why so many exist side by side instead of one replacing all the others.

Layer 1s provide the base security; Layer 2s scale on top of that security; EVM compatibility lets tools travel between networks; and bridges let value move between them: each with its own risks. Understanding these pieces is what lets you choose a network deliberately, instead of by accident.

Glossary

Node

A computer that keeps a copy of a network's ledger and enforces its rules.

Consensus Mechanism

The process by which independent nodes agree on which transactions are valid and in what order.

Validator

A participant responsible for checking and confirming transactions according to the network's consensus mechanism.

Gas

The unit used to measure the computational work required by a transaction.

Gas Fee

The payment, in the network's native token, made to have a transaction processed.

Layer 1

A base blockchain network with its own independent ledger, validators, and consensus mechanism.

Layer 2

A system built on top of a Layer 1 that processes transactions off the base network and periodically settles a summary back to it.

EVM (Ethereum Virtual Machine)

The standardized execution environment for smart contracts that a network can choose to implement.

EVM-Compatible Network

A network that implements the same execution environment as Ethereum, allowing tools and contracts to be reused across it.

Bridge

Infrastructure that allows value or information to move between two otherwise separate networks.

Quiz

Check your understanding of this lesson before moving on. Incorrect answers point you straight back to the relevant section.