Sidechain

Anna holds bitcoin in her own wallet. She wants to try an application unavailable on Bitcoin's main network, or move funds on a network with different features. A sidechain is an independent blockchain: its own transaction record, maintained by nodes, the computers checking its local rules. Transactions are recorded in its own sequence of blocks, each grouping transactions together. It is not a temporary branch of Bitcoin’s history. It can offer functions without requiring every Bitcoin user to adopt them. Anna is nevertheless entering a system with different security assumptions. First she needs to understand how value gets in and how she can get it back. [1]

Imagine a deposit of 0.1 BTC, leaving fees aside for simplicity. On entry, called a peg-in, BTC is locked on the main network under the rules of the connection, or bridge. Anna can then access the corresponding representation on the sidechain, such as 0.1 L-BTC on Liquid. She has not gained another 0.1 BTC that she can also spend on Bitcoin. The original UTXO, an unspent Bitcoin transaction output, has not moved into another database. An output specifies an amount and the conditions for spending it, such as the required signatures. The records are linked but belong to separate histories. A 1:1 ratio describes the intended backing and exchange; it does not promise an immediate withdrawal or an identical price in every market. [1] [9] [15]

To return, Anna uses a peg-out. Depending on the system, the sidechain representation is destroyed or locked, and the bridge releases the corresponding BTC on the main network. This is not an ordinary payment between two Bitcoin addresses. Bitcoin does not normally verify another network's entire history and rules. Release may therefore depend on a designated group's signatures, specialized hardware or other conditions. Anna needs to know who can delay, refuse or wrongfully authorize a withdrawal. A private key is secret data a wallet uses to create signatures for spending funds. Holding her own L-BTC or rBTC keys does not remove those conditions. Trading through a dealer is also different from a direct peg-out and introduces that dealer's price, available funds for the exchange and rules. [1] [9]

Pavel asks who confirms payments on the new network. Anna must add another question: who can spend the BTC locked on Bitcoin? Consensus, the rules for agreeing on valid transactions and history, addresses the first issue. Custody and bridge rules address the second. A functioning sidechain can have withdrawal problems; producing more blocks does not fix a broken bridge. A reorganization of recent sidechain history does not rewrite Bitcoin's history, but can harm local payments and backing. Running a node helps verify local rules. It does not give its operator somebody else's signing keys or the right to release backing BTC unilaterally. [1]

Liquid Network illustrates one model. It uses Elements software, and designated operators sign its blocks instead of ordinary Bitcoin miners producing them. This arrangement is called a Strong Federation; roles known as watchmen manage the Bitcoin bridge. L-BTC represents BTC locked on the main network. Confidential Transactions can hide amounts and asset types, but not automatically every relationship surrounding a payment. Anna must not assume that having her own wallet means withdrawing directly without an intermediary: ordinary Liquid users are not automatically authorized to peg out directly. They normally return through an authorized participant or a swap service. Anna needs to understand that service's terms before entering. [2] [9]

Rootstock runs smart contracts, programs executed under the network's rules. Its environment is compatible with the Ethereum Virtual Machine (EVM), which runs these programs on Ethereum. Participating Bitcoin miners protect its blocks through Merged Mining, reusing the same computational work for both networks. This does not mean that every Bitcoin miner automatically protects Rootstock. Its PowPeg adds another layer: PowHSM devices protect signing keys and follow evidence of accumulated mining work. Operators keep the devices running; they do not normally sign withdrawals manually with freely accessible keys. Deposits release existing rBTC from the bridge, rather than mining new BTC. Security therefore also depends on the mechanism's software, hardware and availability. [10] [11]

The 2014 proposal Enabling Blockchain Innovations with Pegged Sidechains, whose authors included Adam Back and Andrew Poelstra, described a connection in both directions called a two-way peg. It also uses SPV, simplified payment verification. A proof can show a transaction's inclusion in a block and subsequent work recorded in block headers, compact records that link to preceding blocks; that does not automatically validate every transaction across the network. Assumptions about history, waiting periods and responses to reorganizations matter. Practical bridges therefore differ: a federation distributes signing among operators, while other designs add hardware or miner decisions. Merged Mining alone describes mining, not a complete withdrawal solution. [1]

Drivechain offers another approach. The technical proposal BIP 300 proposes approving withdrawals from a special BTC escrow gradually through miner signaling. Bitcoin nodes would track the stipulated withdrawal conditions, not the entire history of every sidechain application. BIP 301 addresses Blind Merged Mining: sidechain block builders would pay Bitcoin miners for inclusion through the proposed mechanism without miners having to run that sidechain application themselves. As of 17 October 2026, both documents have Draft (a proposal still under development) status. A proposal, experimental software and activated main-network rules are different things. A BIP number therefore does not promise Anna that this withdrawal mechanism is available in ordinary Bitcoin Core. [7] [8]

Lightning Network is a network of payment channels. Participants update signed payment states and can close their channel on Bitcoin under its conditions; doing this does not require a shared, separate blockchain. A sidechain does have its own block history. Neither rollup nor Statechain is a synonym: a rollup uses data or proofs published on a base layer, while a Statechain transfers control of a specific Bitcoin output. Exactly what is enforceable, and what trust is required, depends on the design. All these systems may be called an additional layer, but the Layer 2 label alone does not explain who controls the funds or how users can exit. [12] [13] [14]

Anna starts with her purpose: does she need this network's feature, or will a Bitcoin payment do? If a sidechain makes sense, she checks wallet support, the correct network and backups. She establishes which asset pays fees, how entry and exit work, their minimum amounts and whose cooperation they need. Outages, operator changes and emergency procedures matter too: a bridge's emergency mechanism may not be something she can invoke herself. Only then does she try a small transfer in both directions. A successful trial can reveal procedural mistakes, but cannot prove the bridge will remain secure. A sidechain expands what she can do; it does not make her trust decisions for her. [1] [9]