Sidechains, Bridges & Other Paths
Alternatives to rollups, and the risks of moving assets between chains.
Lesson map
Sidechains: related, not secured by
A sidechain is its own independent blockchain, connected to a main chain via a bridge - but running its own consensus and its own validators. That's the crucial difference from a rollup: a sidechain does not inherit the main chain's security, no matter how closely it's associated with it.
Sidechains can be fast and cheap precisely because they aren't constrained by posting proofs back to a Layer 1. The cost is that you're trusting the sidechain's own validator set, separately from whatever chain it's connected to.
State channels and sharding
A state channel lets a small group of participants transact directly with each other off-chain, as many times as they like, and only settle the final outcome on the base layer once. It's fast and cheap for that narrow use case, but only really works for participants known in advance.
Sharding takes a different angle: instead of adding a layer on top, it splits the base layer itself into multiple parallel shards that each handle a portion of the network's data and transactions, then coordinates between them.
Bridges: the connective tissue - and the risk
Moving an asset from one chain to another almost always goes through a bridge: tokens get locked (or burned) on the origin chain, and an equivalent representation is minted on the destination chain. Bridges are what let a single asset feel usable across many chains and Layer 2s.
They're also one of the most attacked parts of the entire ecosystem. A bridge concentrates a large pool of locked assets behind whatever validates the lock-and-mint process - smart-contract bugs or a compromised validator set there can be catastrophic, and unlike a rollup, a bridge to a separate chain doesn't get L1-level security for free.
Remember
Before bridging meaningful value, check who or what actually secures the bridge - a multisig, a validator set, or light-client verification each carry very different risk.
Concept map · schematic
Execution and Ethereum settlement
A conceptual rollup lifecycle; actual guarantees vary by network.
- 01
Layer 2
Orders and executes transactions on its own chain
- 02
Publish data
Posts commitments and data through L1 transactions or blobs
- 03
Settlement
Applies proof/challenge rules to secure resulting state
Important: A sequencer confirmation is not identical to final settlement on Ethereum.
Self-check
Check your understanding
Choose an answer for each question, then check the results and explanations.
Primary references
Documentation and standards
References added
Official technical references for further verification. A source link is not a guarantee that every earlier editorial sentence has been reverified; provider specifications may also change over time.
The curriculum predates this reference index. These sources are offered to check technical details; no original publication date has been inferred.
- Optimistic rollupsethereum.orgRead source ↗
- EIP-4844 blob transactionsEthereum Improvement ProposalsRead source ↗
Apply what you learned
Related practical guides
Cross-Chain Bridging, Explained
What a bridge actually coordinates between networks, what to verify in a quote and why destination certainty matters.
Read guide →Bridge Fees vs. Slippage
Separate network and protocol fees from execution slippage so you can compare cross-chain quotes on the number that matters: what arrives.
Read guide →
Continue learning