Chain
A blockchain network with its own consensus and state.
A chain is a blockchain network that maintains an ordered ledger and current state under a defined set of consensus rules. Participants use compatible node software to verify transactions and blocks. In everyday Web3 language, chain may refer to a Layer 1 network, a rollup, a sidechain, or an application-specific blockchain.
Sovereign chains choose their own validators or miners and determine finality through their native consensus. Bitcoin and Ethereum are Layer 1 chains. A sidechain also has separate consensus but connects assets or messages through bridges. Rollups publish data and state commitments or proofs to a base layer, using that chain for part of their security and settlement while maintaining separate execution state.
Each chain has its own native asset, address rules, transaction fees, block timing, and application environment. EVM-compatible chains can use familiar Ethereum tools and address formats, but compatibility does not make them the same network. Identical addresses may exist on multiple chains with unrelated balances. Wallets use network configuration and chain IDs to direct requests to the correct system.
Chains matter because deployment choice affects security, cost, user experience, and access to liquidity. A cheap network may offer fast application interactions but rely on a small validator set or weak bridge. A highly decentralized base layer may have expensive block space. Developers often balance these properties by deploying on a Layer 2 or supporting several networks.
Cross-chain applications add complexity. Assets represented on another chain depend on the bridge or issuer that created them. Messages can be delayed by finality, relayers, challenge periods, or outages. Teams must track deployments, contract addresses, indexing, nonce behavior, and incident response separately for every supported chain. Testing only one environment leaves important failure modes unexamined.
Before using a chain, confirm its official wallet settings, native fee asset, explorer, bridge routes, and finality expectations. Never send an asset merely because the destination address format looks compatible. Builders should document dependencies and provide clear network switching. A chain is an independent execution and state environment, and users receive only the security guarantees of that network plus every bridge, contract, and operator involved in their activity.
Frequently asked questions
- A sovereign chain uses its own consensus participants to order transactions and determine canonical state. A rollup executes transactions separately but posts data and commitments or proofs to a base layer for settlement. Rollups still have their own nodes and sequencing, while security also depends on contracts, data availability, upgrade controls, and the user's ability to exit.
- Yes, through bridges, messaging protocols, light clients, external validator networks, or shared interoperability standards. These systems verify or attest to events on another chain, then act locally. Cross-chain communication adds trust and failure assumptions beyond either network. Users should examine message verification, finality, administrators, and recovery behavior rather than assuming connected chains share identical security.
- Evaluate where target users and liquidity already exist, then compare security, finality, fees, throughput, data availability, wallets, developer tools, indexers, and reliable infrastructure. Consider contract language, upgrade process, regulatory needs, and bridge dependence. Test performance during congestion and estimate ongoing operational costs. Choosing solely by advertised transaction speed can create expensive security and distribution problems.