A sidechain is an independent blockchain that runs alongside a mainchain (such as Ethereum or Bitcoin) and connects to it through a two-way peg. Assets move between the two chains by locking them on the mainchain and minting equivalent tokens on the sidechain. The sidechain operates with its own validators, consensus rules, and block parameters, separate from the mainchain entirely.
​

Sidechains emerged as one of the earliest approaches to blockchain scaling. The core idea is straightforward: instead of forcing every transaction through a single chain's throughput ceiling, you route activity onto a parallel chain that can handle higher volumes or apply different rules, while keeping a financial link back to the base layer.
​

The term "sidechain" is sometimes used loosely to mean any chain connected to another. In practice, what distinguishes a true sidechain from a rollup or a layer 2 solution is where security comes from. A sidechain relies on its own validator set, not on the mainchain's consensus, to guarantee the validity of transactions. That distinction matters enormously when evaluating the trust assumptions you accept when moving assets across chains.
​

For broader context on how chains communicate with each other, see What Is Blockchain Interoperability. For the base layer that sidechains peg to, see What Is a Layer 1 (L1) Blockchain.
​

Sidechains operate through a two-way peg: assets lock on the mainchain, an equivalent amount mints on the sidechain, and burning those tokens releases the originals. The sidechain runs its own consensus, confirming transactions at whatever speed and cost its design allows, without waiting for the mainchain to validate individual blocks.
​

The two-way peg is the technical core of any sidechain. On the locking side, a user sends assets (ETH, BTC, or an ERC-20 token) to a bridge contract on the mainchain. That contract records the deposit and either calls a relay or waits for validators to observe and confirm it. Once confirmed on the mainchain, the sidechain's bridge component mints a wrapped version of those assets, denominated 1:1 with the original.
​

Exiting works in reverse. A user initiates a burn transaction on the sidechain, destroying the wrapped tokens. A similar relay process confirms the burn to the mainchain contract, which releases the original assets. The security of this exit process depends entirely on who controls the bridge contract and how many validators must sign off before releasing funds.
​

Because the sidechain has its own validator set, it can apply radically different parameters than the mainchain. Polygon PoS, for example, runs a proof-of-stake consensus among a few hundred validators and produces blocks every two seconds, compared to Ethereum's twelve-second slot time. Polygon PoS checkpoints its state root to Ethereum periodically, but individual transactions are confirmed by Polygon's own validator network, not by Ethereum's.
​

Gnosis Chain (formerly xDai) uses a similar architecture, running its own proof-of-stake validator set while checkpointing and pegging to Ethereum. Gnosis Chain was designed specifically for stable payments, originally using DAI as its native gas token.
​

On Bitcoin, the Liquid Network operates as a federated sidechain. Rather than a decentralized validator set, Liquid uses a federation of known functionaries (exchanges and companies) who jointly control the peg. Liquid Network enables faster Bitcoin settlement and confidential transactions but inherits the trust assumptions of that federation.
​

Consensus independence is what gives sidechains their throughput advantage. The mainchain does not validate each sidechain block. The sidechain's validators do. This removes the bottleneck but also removes the security backstop, a tradeoff covered in detail below.
​

It is worth being precise about what "pegged" means in practice. The peg is a financial link, not a security link. The mainchain does not attest to the correctness of sidechain transactions; it only holds the collateral. Whether the sidechain state actually reflects what users deposited is a question answered solely by the sidechain's own validators. This is fundamentally different from a rollup, where the mainchain can reject fraudulent withdrawals by verifying a fraud proof or validity proof before releasing funds.
​

Bridge designs also vary in how they handle chain reorganizations. If a sidechain reorganizes its history (rolls back blocks), the bridge must handle a situation where a deposit that was confirmed on the sidechain is now unconfirmed. Most production bridges require a certain number of block confirmations before processing deposits or withdrawals to mitigate this. The number of required confirmations is a direct expression of the sidechain's finality guarantees.
​

The key difference is where security comes from. A sidechain secures itself with its own validators; if they collude, user funds are at risk. Rollups post transaction data or proofs to the mainchain so Ethereum's consensus ultimately backstops them. That makes rollups stronger on security but adds cost and latency that sidechains avoid.
​

The practical consequence of this difference shows up at the bridge. When you withdraw from a rollup, the mainchain can verify independently that the withdrawal is valid, either by checking a fraud proof (optimistic rollups) or a validity proof (ZK rollups). When you withdraw from a sidechain, the mainchain contract simply trusts that the bridge's validators reported the burn correctly. There is no mainchain-level proof of the sidechain state.
​

For a full breakdown of rollup mechanics, see What Is a Rollup: Optimistic vs ZK Rollups.
​

L2Beat tracks risk ratings for rollups and distinguishes them from sidechains. Reviewing L2Beat's scaling summary shows that chains classified as sidechains receive lower security ratings than rollups in the same ecosystem, which reflects exactly the tradeoff in the table above.
​

A sidechain's security is only as strong as its validator set. If a majority of those validators collude, they can produce fraudulent state transitions, steal bridged funds, or censor exits. Rollups avoid this by inheriting Ethereum's consensus, but sidechains carry the full weight of their own operator honesty as the core trust assumption.
​

The bridge contract on the mainchain is the highest-risk component. It holds all the assets that have been locked in exchange for sidechain tokens. Whoever controls the keys to that contract controls those assets. Different sidechain architectures manage this differently.
​

In a federated peg (like Liquid Network), a defined group of known entities holds multisig keys. The system is transparent about who the signers are, but users must trust those specific parties not to collude. In a delegated proof-of-stake sidechain (like early Polygon PoS), validators stake tokens as collateral, creating an economic disincentive to misbehave. But the stake can be much smaller than the total value locked in the bridge, which means a profitable attack is possible if TVL grows faster than validator stake.
​

The Ronin Network hack in March 2022 is the most cited example of sidechain bridge failure. Ronin was built as a sidechain for Axie Infinity, a blockchain game. Its bridge was secured by a 5-of-9 validator multisig. An attacker compromised private keys from five validators, including four controlled by Sky Mavis (the Axie developer) and one controlled by the Axie DAO. With five signatures, they drained approximately $625 million in ETH and USDC from the bridge contract. The attack was not discovered for six days. Ronin subsequently rebuilt with a larger validator set and additional security controls, but the incident demonstrated concretely what validator centralization means for user funds.
​

When evaluating a sidechain, the questions that matter are: how many validators does the bridge require? How large is their combined stake relative to the TVL? Are validators public entities with reputational stakes, or anonymous? What is the process for upgrading the bridge contract, and who controls it? For an explanation of the trustless ideal that rollups approximate more closely, see What Does Trustless Mean.
​

Sidechains are not a single category. They range from general-purpose EVM-compatible chains to application-specific sovereign networks to hybrid constructions that borrow from both sidechain and rollup designs. Understanding the subtypes helps clarify which tradeoffs apply to any specific chain you are evaluating.
​

EVM-compatible sidechains are the most common type for Ethereum. These chains run the same Ethereum Virtual Machine, accept Solidity contracts with no modifications, and support the same tooling (Hardhat, Foundry, MetaMask). Polygon PoS and Gnosis Chain are canonical examples. Teams deploy to them because migration from Ethereum mainnet is nearly frictionless, gas costs are a fraction of mainnet rates, and transaction throughput is dramatically higher.
​

App-specific or sovereign sidechains are built for a single application or narrow category of use cases. Ronin Network was built exclusively for Axie Infinity. DFK Chain was built for DeFi Kingdoms. These chains customize block time, gas limits, validator requirements, and sometimes the consensus mechanism itself for their specific workload. The tradeoff is that their validator sets are often small and closely affiliated with the application developer, which concentrates risk.
​

Plasma chains were an early Ethereum scaling proposal that sits conceptually between a sidechain and a rollup. Plasma chains commit block headers to Ethereum and allow users to exit to the mainchain by submitting fraud proofs if an operator misbehaves. This gives Plasma better security guarantees than a pure sidechain, but the data availability problem (users must monitor the chain and can be forced to exit in a mass-exit scenario) led to Plasma being largely superseded by rollups. Ethereum's Plasma documentation covers the architecture in detail.
​

Validiums are a hybrid construction: they use ZK validity proofs posted to Ethereum (like a ZK rollup) but store transaction data offchain (like a sidechain). This gives them stronger proof-based security than a sidechain while retaining low costs, but introduces a data availability risk: if the offchain data provider goes offline or withholds data, users may be unable to reconstruct their state and exit. StarkEx (used by dYdX v3 and Immutable X) operates as a validium.
​

Sidechains and layer 2 solutions are often conflated but they are architecturally distinct. A rollup posts data or proofs onchain so the mainchain can independently verify state. A sidechain runs its own consensus and connects through a bridge, without inheriting mainchain security. The distinction determines how much risk transfers to you when your assets leave the base layer.
​

That said, sidechains make sense in specific situations where the tradeoff is worth accepting.
​

When throughput requirements exceed what rollups currently offer, sidechains can fill the gap. A gaming application processing thousands of microtransactions per second, where individual transactions have low value, may accept sidechain security in exchange for the throughput it needs. The expected loss from a security failure is lower when per-transaction value is small.
​

When an application needs independent governance, a sidechain gives the development team control over protocol parameters without being bound by the mainchain's upgrade schedule. A sidechain can modify gas pricing, block times, transaction ordering rules, or consensus parameters. A rollup that inherits Ethereum's security cannot diverge from Ethereum's fundamental rules in the same way.
​

When the application requires rules the mainchain cannot execute, a sidechain can implement entirely custom transaction types or privacy features. Liquid Network's confidential transactions obscure transaction amounts, something Bitcoin's base layer does not support natively.
​

Fee denomination is another practical consideration. A sidechain can designate any token as its native gas currency, while Ethereum rollups pay fees in ETH. Gnosis Chain originally priced gas in DAI, a stablecoin, so users knew their transaction costs without tracking ETH price. That design decision was possible precisely because Gnosis Chain runs its own fee market, independent of Ethereum's.
​

Developer teams also choose sidechains when they want to iterate quickly on protocol rules without governance dependencies. Upgrading a rollup's dispute resolution contract on Ethereum requires coordination with Ethereum's broader upgrade cycle and may involve timelocks or multisig delays. A sidechain with its own governance can modify parameters through whatever process its validators agree to, which is faster but also concentrates protocol power in that validator group.
​

For applications where user funds are large and security is paramount, rollups are the more defensible choice today. L2Beat categorizes major scaling solutions by their security model, and the separation between rollups and sidechains in their risk framework reflects the real difference in what users are trusting. For a direct comparison of cross-chain transfer mechanisms, see What Is a Blockchain Bridge.
​

The most widely used sidechains today demonstrate the range of design choices available: from general-purpose EVM chains processing millions of daily transactions to Bitcoin-native federated networks serving specific financial use cases. Each illustrates different points on the security and throughput tradeoff curve.
​

Polygon PoS is the highest-traffic Ethereum sidechain by transaction volume and unique addresses. It runs a delegated proof-of-stake consensus among a validator set that stakes MATIC (now POL) tokens. Polygon PoS checkpoints its state root to Ethereum approximately every thirty minutes using a set of checkpoint validators. Daily transaction volumes regularly exceed five million, compared to Ethereum mainnet's approximately one million. Gas fees on Polygon PoS average fractions of a cent. The chain has processed payments for companies including Stripe, Reddit, and Starbucks. Polygon PoS documentation describes the full architecture.
​

Gnosis Chain (formerly xDai Chain) launched in 2018 specifically for stable value transfers. It originally used DAI as its native gas token so users could transact without needing to hold a volatile asset for fees. Gnosis Chain now uses GNO as its staking token and has transitioned to a proof-of-stake consensus compatible with Ethereum's validator design. It serves as infrastructure for prediction markets (Gnosis built Omen), payments, and DAOs. Gnosis Chain remains notable as one of the few chains designed around stable-denomination fees from the start.
​

Liquid Network is a federated Bitcoin sidechain operated by Blockstream. It enables faster Bitcoin settlement (approximately two minutes versus ten for Bitcoin mainnet) and supports confidential transactions that hide amounts. The federation consists of exchanges, brokers, and financial institutions who collectively manage the peg. Liquid is used primarily by traders moving BTC between exchanges and by issuers of tokenized assets on Bitcoin. It does not run a decentralized validator set; trust is placed in the named federation members.
​

Ronin Network was built by Sky Mavis to support Axie Infinity's onchain economy. At its peak in 2021, Axie was generating hundreds of thousands of daily active users whose NFT trading and token earnings would have been uneconomical on Ethereum mainnet at the time. Ronin solved the cost problem but concentrated bridge security in a small validator set. After the March 2022 hack, Sky Mavis rebuilt Ronin with twenty-two validators, delegated staking, and a proof-of-stake architecture requiring twelve of twenty-two validators to authorize bridge withdrawals. The rebuilt Ronin represents a reasonable case study in how app-specific sidechains respond to security failures at scale.
​

No. Layer 2 solutions like rollups derive their security from the mainchain by posting transaction data or proofs onchain. Sidechains run independent consensus processes and connect to the mainchain only through a bridge, without inheriting mainchain security guarantees. A sidechain failure does not affect the mainchain, but sidechain users carry the trust risk of the sidechain's own validator set.
​

It depends on the bridge design. If the sidechain shuts down orderly and the bridge contract is still functional, you can initiate a withdrawal to reclaim assets on the mainchain. If the bridge validators disappear or the contract is abandoned, assets can be permanently stranded on the sidechain. This is why bridge contract governance and validator set continuity are critical evaluation criteria before bridging large amounts.
​

Polygon PoS is technically a sidechain. It runs its own validator set and does not post full transaction data to Ethereum. Polygon itself has historically described it as a "commit chain," but independent analysis (including L2Beat's classification) categorizes it as a sidechain because Ethereum cannot independently verify sidechain state transitions. Polygon's newer chains (zkEVM, CDK) are genuine rollups with different security properties.
​

A two-way peg is the mechanism that ties a sidechain's assets to the mainchain. Locking assets on the mainchain lets you mint equivalent tokens on the sidechain; burning them lets you reclaim the originals. It matters because the peg's security determines whether you can always exit back to the mainchain at full value. A poorly designed peg is the most common attack surface on sidechain-connected bridges.
​

Yes, architecturally this is possible, and Polygon has pursued this path. Polygon PoS is being upgraded toward a validium architecture that posts ZK proofs to Ethereum, improving security guarantees while preserving the existing chain state. Moving from sidechain to rollup requires posting transaction data or proofs onchain, which increases costs, so the transition involves real tradeoffs in fee economics and throughput.
​

By Eco Team. Last updated April 30, 2026.
​

Sources: Ethereum.org Plasma docs; L2Beat Scaling Summary; Polygon PoS documentation; Liquid Network; Gnosis Chain; Ronin Network.
​