Scaling and Interoperability

An atomic swap is a method for exchanging assets between parties so that the protocol aims to complete both sides of the exchange or allow refunds, rather than leave one party paid and the other unpaid. A common design uses hash time-locked contracts: one participant commits to a secret's hash, and revealing the secret to claim one asset enables the other participant to claim the corresponding asset. Different deadlines provide refund paths when the exchange does not finish. The participating networks must support compatible cryptographic and timing mechanisms. Atomic does not mean instantaneous, free, or completely riskless. Users still face transaction fees, confirmation delays, monitoring requirements, and implementation errors. Cross-chain reorganizations and poorly chosen timeouts can also matter. Unlike a custodial exchange, the arrangement seeks to avoid handing both assets to an intermediary, but careful protocol design and reliable wallet software remain essential.

Sources: github.com

A bridge is a system that transfers assets, messages, or representations of value between blockchain environments. One common asset design locks coins on an origin network and creates corresponding tokens elsewhere; another destroys a representation before releasing the original asset. The precise mechanism varies, and the destination token is not automatically identical to native coins on its source chain. Bridges may rely on custodians, signer groups, smart contracts, external validators, or cryptographic verification. Each design introduces different assumptions about who can authorize transfers and what happens during failures. A secure underlying blockchain does not remove weaknesses in the bridge connecting it to another system. Relevant risks include contract errors, compromised signing keys, false messages, unavailable liquidity, and suspended redemption. Evaluating a bridged asset therefore requires understanding both chains and the mechanism responsible for maintaining and returning its backing.

Sources: ethereum.org

Layer 2 refers to a system built above a base blockchain to handle some activity outside the base chain while using it for settlement or enforcement. The term covers different designs, so the actual relationship to the underlying chain matters more than the marketing label. Bitcoin's Lightning Network uses payment channels, while Ethereum rollups use different methods for executing transactions and establishing their results. A separate chain or custodial service does not automatically become a layer 2 merely because it accepts deposits from a well-known network. Important distinctions include who can withdraw funds, what information remains available, how disputes are resolved, and whether a privileged operator can halt activity. Faster or cheaper transactions can come with liquidity requirements, exit delays, or additional software assumptions. Layer 2 therefore describes an architectural relationship, not a universal guarantee of base-layer security in every circumstance.

Sources: ethereum.org · docs.lightning.engineering

The Lightning Network is a Bitcoin payment-channel network that allows participants to make transfers without recording every individual payment directly on Bitcoin's blockchain. Channel participants commit funds through on-chain transactions and exchange updates that represent changing balances. Payments can be routed across connected channels, subject to available liquidity and the network's payment protocols. Opening or closing channels can require on-chain fees, and routed payments can carry forwarding fees. Lightning does not introduce a separate native mining token: payments are denominated in bitcoin units. Its security and usability depend on wallet design, channel management, monitoring arrangements, and the ability to use on-chain enforcement when necessary. Some services provide custodial Lightning accounts, which add provider risk rather than giving the user direct control of channel funds. A fast Lightning payment should therefore be distinguished from a new on-chain transaction and its confirmations.

Sources: github.com · docs.lightning.engineering

A sidechain is a separate blockchain connected to another network through a mechanism for transferring or representing assets. It can offer different execution capabilities, block timing, or transaction rules while maintaining its own ledger and consensus arrangements. Moving BTC into a Bitcoin-related sidechain usually involves a peg or bridge that controls how the original coins are locked and how they can be released. The sidechain asset is therefore subject to additional assumptions beyond Bitcoin's ordinary spending rules. Some sidechains use merged mining, while others rely on validators or federations; sharing some infrastructure does not make every design equally secure. A sidechain should not automatically be described as inheriting all base-chain security or as a rollup. The critical questions concern validation, withdrawal authorization, operator control, and what happens when the bridge or sidechain stops functioning. Those details determine the practical relationship between the two networks.

Sources: ethereum.org · dev.rootstock.io