Sidechain

Overview

A Sidechain runs its own Blockchain Protocol and canonical history while maintaining a connection to another chain. Users typically lock or otherwise account for assets on the source chain and receive a representation on the sidechain through a bridge.

Sidechains can change block time, gas rules, validator membership, virtual-machine support, or governance to target a particular workload. These choices can reduce fees and improve throughput, but they create a security model independent from the parent chain’s consensus.

A sidechain differs from a rollup. Rollups publish transaction data or proofs to a base layer and rely on that layer for parts of settlement, while a sidechain generally validates its own state through its own consensus. The boundary can be obscured by marketing, so technical documentation matters.

Moving value creates a Bridged Asset and adds bridge risk. Users depend on custody, validator signatures, smart contracts, proofs, or other mechanisms that control minting and redemption. A sidechain transaction can be final on that chain while the exit to the parent chain remains delayed or challenged.

Payment integrations should identify the exact sidechain network, asset contract, fee asset, bridge route, and Finality Policy. An address compatible with Ethereum tools does not make the chain Ethereum Mainnet. Provider support and liquidity should be confirmed before accepting or settling funds.

Exit design is a central operational question. A sidechain may finalize quickly internally while bridge withdrawal requires additional signatures, challenge periods, or liquidity. Merchants should measure settlement at the layer where funds become usable for their actual treasury or refund workflow.