Sidechain

What Is a Sidechain?

A sidechain is a separate blockchain that runs alongside a parent chain and allows assets to move between the two. The parent chain (often called the "mainchain") and the sidechain are connected through a mechanism called a two-way peg, which ensures that the total supply of the asset remains constant across both chains. When you move Bitcoin to a sidechain, the BTC is locked on the main chain and an equivalent amount of the pegged asset is created on the sidechain. When you move it back, the sidechain tokens are destroyed and the original BTC is unlocked.

The concept was first formally described in the 2014 paper "Enabling Blockchain Innovations with Pegged Sidechains" by Back et al. The motivation was straightforward: Bitcoin's conservative approach to protocol changes makes experimentation slow and risky. Sidechains provide a way to try new features (faster blocks, different scripting languages, confidential transactions) without requiring consensus changes on Bitcoin itself.

Unlike rollups, which post transaction data or proofs back to the parent chain for verification, sidechains maintain their own consensus and security model. This gives them more flexibility but introduces different trust assumptions: the security of your funds on a sidechain depends on the sidechain's own validators and the integrity of the peg mechanism, not on Bitcoin's proof-of-work.

How It Works

The core mechanism of any sidechain is the two-way peg. This is the system that transfers value between the mainchain and the sidechain while maintaining a 1:1 backing ratio. The basic flow works as follows:

1. A user sends BTC to a special peg-in address on the Bitcoin mainchain. This transaction locks the coins so they cannot be spent on Bitcoin until they are pegged back out.
2. After a confirmation period (to prevent double-spend attacks), the sidechain recognizes the deposit and mints an equivalent amount of pegged tokens (for example, L-BTC on Liquid).
3. The user transacts freely on the sidechain using the pegged tokens, benefiting from whatever features the sidechain offers: faster confirmation, lower fees, confidential transactions, or smart contracts.
4. When the user wants to move funds back, they initiate a peg-out by burning the sidechain tokens and providing a Bitcoin address.
5. The peg mechanism releases the locked BTC on the mainchain and sends it to the specified address.

The critical question is: who controls steps 1 and 5? Who decides when to lock and unlock the mainchain BTC? This is where different sidechain designs diverge.

Federated Pegs

The most widely deployed peg mechanism is the federated peg, used by Blockstream's Liquid Network. In a federated model, a predefined group of entities (called functionaries) collectively custody the pegged Bitcoin using a threshold signature scheme.

The peg-in address is a multisig controlled by the federation. To release funds during a peg-out, a threshold of functionaries (for example, 11-of-15) must sign the Bitcoin transaction. This means users trust that a supermajority of functionaries will not collude to steal the pegged funds.

# Simplified federated peg flow

# Peg-in: user sends BTC to federation multisig
bitcoin-cli sendtoaddress <federation_multisig_address> 1.0

# After confirmations, Liquid mints L-BTC
# (handled automatically by federation watchmen)

# Peg-out: user requests withdrawal on Liquid
elements-cli sendtomainchain <bitcoin_address> 1.0

# Federation functionaries co-sign the release
# Requires 11-of-15 signatures to unlock mainchain BTC

Liquid's federation currently consists of cryptocurrency exchanges, financial institutions, and infrastructure providers. The federation also produces sidechain blocks, achieving 1-minute block times compared to Bitcoin's 10-minute average.

Drivechain Proposals

Drivechains (BIP-300 and BIP-301) propose a different model where Bitcoin miners validate peg-outs instead of a federation. Under this design, miners collectively decide whether to approve withdrawal transactions from the sidechain through a slow, multi-month voting process.

The idea is that miners have economic incentives to protect the peg because stealing funds would damage Bitcoin's value and therefore their mining revenue. A withdrawal requires sustained miner approval over approximately six months, giving the community time to detect and respond to malicious attempts.

Drivechains remain a proposal and have not been activated on Bitcoin. They would require a soft fork to add new opcodes (OP_DRIVECHAIN and OP_NOP5) to Bitcoin Script. The proposal is controversial: proponents argue it would unlock permissionless sidechain creation, while critics worry about miner extractable value and the security implications of giving miners custody authority over pegged funds.

SPV Pegs

The original sidechain whitepaper proposed SPV (simplified payment verification) pegs, where each chain could verify transactions on the other using block headers and Merkle proofs. The sidechain would verify that a peg-in transaction was included in a valid Bitcoin block by checking the Merkle proof against the block header.

Pure SPV pegs have never been implemented for Bitcoin because they would require a consensus change: Bitcoin nodes would need the ability to validate sidechain block headers to process peg-outs. This is essentially what drivechains attempt to solve with a different verification mechanism.

Bitcoin Sidechains

Liquid Network

Liquid is the most prominent Bitcoin sidechain, operated by Blockstream since 2018. It targets traders and financial institutions who need fast, confidential Bitcoin transfers. Key features include:

• Confidential Transactions: amounts and asset types are hidden from public view using cryptographic commitments, while remaining verifiable by transaction participants
• 1-minute block times with 2-block finality: transactions settle in approximately 2 minutes compared to Bitcoin's typical 60-minute wait for 6 confirmations
• Issued Assets: anyone can create tokens on Liquid, enabling stablecoins, security tokens, and other wrapped assets to exist on a Bitcoin sidechain
• Support for SegWit and script extensions beyond what Bitcoin's mainchain currently offers

RSK (Rootstock)

RSK brings Ethereum-compatible smart contracts to a Bitcoin sidechain. It uses a merge-mining model where Bitcoin miners simultaneously mine RSK blocks, leveraging Bitcoin's hashrate for security. The peg mechanism (called PowPeg) uses specialized hardware modules held by federation members, with merge-mining providing an additional security layer.

RSK's EVM compatibility means developers can deploy Solidity smart contracts using BTC (bridged as RBTC) as the native asset. This enables DeFi applications, lending protocols, and other programmable finance use cases on a Bitcoin-pegged chain.

Sidechains vs. Other Scaling Approaches

Understanding how sidechains compare to other Bitcoin scaling solutions helps clarify when each approach is appropriate:

The fundamental difference is security inheritance. Rollups post proofs or data to the parent chain, so users can always verify the state and exit independently. Sidechains have their own validators, meaning users depend on the sidechain's honesty and liveness to retrieve their funds. This is similar to using a cross-chain bridge: you are trusting the bridge operators with your assets for the duration of the peg.

Newer Bitcoin Layer 2 designs like Spark take a different approach by using statechains and threshold signatures to enable off-chain transfers without requiring a separate blockchain or consensus mechanism.

Use Cases

Sidechains serve specific needs that the Bitcoin mainchain cannot efficiently address:

• Confidential trading: Liquid enables private transfers between exchanges and institutions without exposing amounts on a public ledger
• Smart contract experimentation: RSK allows developers to build programmable applications using BTC as collateral, without waiting for new opcodes on Bitcoin
• Token issuance: sidechains can support token standards for stablecoins, security tokens, and NFTs pegged to Bitcoin's security budget
• Protocol testing: new consensus mechanisms, covenant designs, or transaction formats can be tested on a sidechain before proposing mainchain changes. This is detailed further in research on Bitcoin covenants
• Faster settlement: applications requiring sub-minute confirmation times can use sidechains with shorter block intervals while still denominating value in BTC

Risks and Considerations

Peg Security

The most significant risk with any sidechain is the peg. In a federated model, the federation members collectively hold all the pegged BTC. If a sufficient number of functionaries collude or are compromised, they can steal the funds. Unlike Bitcoin's mainchain where your UTXOs are secured by the full network hashrate, sidechain funds are only as secure as the peg mechanism.

This is not a theoretical concern: bridge exploits across the crypto ecosystem have resulted in billions of dollars in losses. While Bitcoin federated sidechains have not experienced a peg failure to date, the trust model is fundamentally different from holding BTC on the mainchain.

Reduced Decentralization

Sidechains typically have fewer validators than the Bitcoin mainchain. Liquid's federation has approximately 65 members, with 15 acting as block signers at any time. RSK's PowPeg relies on a smaller set of hardware-secured nodes. This concentrated validator set makes sidechains more vulnerable to censorship and regulatory pressure than Bitcoin itself.

Withdrawal Delays and Restrictions

Peg-out processes are not instant. Liquid peg-outs typically require multiple confirmations and federation processing time. Drivechain proposals involve withdrawal periods of several months. During network disruptions or federation issues, peg-outs could be delayed or temporarily unavailable, meaning users cannot freely exit to the mainchain at will.

Consensus Fragmentation

Each sidechain introduces its own consensus rules, node software, and governance structure. This fragments the ecosystem: developers must choose which sidechain to build on, users must evaluate the security of each peg, and liquidity is split across multiple chains. This is a tradeoff inherent in the sidechain model: flexibility comes at the cost of ecosystem fragmentation.

This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.