Glossary
A
Atomic swap
An exchange of crypto assets that does not require a trusted third party. Atomic swaps leverage smart contracts to ensure both parties fulfill transaction obligations before the swap is completed, otherwise, the transaction is canceled, and funds are returned to their respective owners. Atomicity refers to guarantee of a single, individible outcome, i.e., one token transfer cannot execute without its counterparty transfer also executing. In the context of Bitcoin, atomic swaps enable the seamless exchange of BTC with other cryptocurrencies in a secure and decentralized manner.
B
Bitcoin layer
A deliberately ambiguous term that encapsulates L2s, sidechains, state chains, and other networks 'aligned' with either Bitcoin (the network) or BTC (the asset).
Bitcoin Script
A low-level Assembly-based programming language used to define the conditions under which a Bitcoin UTXO can be spent.
Blind merge mining
A technique that allows miners to simultaneously mine multiple blockchains without needing to be fully aware of the contents of the additional chains.
C
Challenge period
A security mechanism that enables anyone to contest a (sometimes fraudulent) state transition within a given time frame. If a challenge period passes without a challenge, the state transition is considered finalized.
Client side validation (CSV)
A paradigm to allow each data kept outside bitcoin transactions (onchain) under Bitcoin consensus rules. This sees users verify transactions and state transitions independently.
Consensus mechanism
A procedure used to reach a collective agreement regarding the status of a data set or the ledger's state. Consensus mechanisms consists of several parts, such as Sybil resistance mechanisms (e.g., PoW, PoS, PoA), leader selection algorithms, and vote-power weighting systems.
Covenant
A mechanism that allows users to impose constraints on how BTC (a UTXO) can be transferred in future transactions.
D
Data availability
The publishing of transaction data which is required to verify transactions, satisfy proving schemes, or otherwise progress the chain. Specifically, a node will verify data availability when it receives a new block that is getting added to the chain. The node will attempt to download all the transaction data for the new block to verify availability. If the node can download all the transaction data, then it successfully verified data availability, proving that the block data was actually published to the network.
Discrete Log Contract (DLC)
A type of smart contract designed to facilitate financial agreements on the Bitcoin network using oracles to provide external data. DLCs enable the creation of complex financial instruments, such as options and futures, by using cryptographic techniques to ensure that the contract is executed based on the outcome of real-world events.
E
Ethereum Virtual Machine (EVM)
A software that sets the rules of computing the state of the Ethereum network from block to block. It serves as the runtime environment for executing smart contracts and decentralized applications.
F
Federated peg
A two-way peg (bridge) controlled by a federation (a permissioned group of overseers). A group of trusted and permissioned parties (the federation) oversees the transfer process, ensuring the security and integrity of the assets being moved.
Forced inclusion
A mechanism for increasing censorship resistance in a Bitcoin layer. It enables a single participant to circumvent sequencer censorship by submitting their transaction directly to the L1 inbox contract. This forces the sequencer to include the transaction in the upcoming batch.
Fraud proof
A cryptographic proof that enables challengers to contest a proposed state transition that contains invalid or fraudulent transactions. Networks that use fraud proofs (e.g., optmistic rollups or optimiums) initially assume that new blocks are valid, then rely on users or watchtowers to challenge blocks if they include invalid state transitions, which are then resolved on the L1.
Full node
A node actor that validates all transactions. A full node verifies and enforces all the rules of the network, rather than only verifying headers (such as light client nodes do). Full nodes do not participate in block production (such as PoW miner nodes or PoS validator nodes do) or store a full copy of a blockchain's history (such as archival nodes do).
L
Layer 1 (L1)
A sovereign network that performs all four core functions of a crypto network: consensus, security, data availability, and execution. In this context, Bitcoin is the L1.
Layer 2 (L2)
A modular network with dedicated execution. L2s rely on an underlying L1 for consensus, security, and data availability, with the ability for users to unilaterally remove funds from the L2 through an L1 transaction.
M
Maximal Extractable Value (MEV)
The maximum value block producers (miners or validators) can obtain by including, reordering, or excluding transactions when producing a new block. MEV is also known as miner extractable value in PoW systems. Nearly all consensus systems create, for short periods of time, privileged actors (e.g., the miner with the right to produce the next block) which have asymmetric knowledge or control over transactions; for sophisitacted actors, this asymmetric position allows them to make financial gains at the expense of other users. Less-sophisticated block producers will have trouble capitalizing on MEV opportunities and could be priced out of the role over time if margins are thin, leading to centralization.
Merge mining
A consensus strategy in which a sidechain (L1) uses a similar consensus mechanism to Bitcoin, with the same PoW hashing algorithm. By using the same algorithm for consensus, Bitcoin miners can opt-in to securing and producing blocks for the sidechain with essentially no additional costs (i.e., reusing the same β€œwork” from Bitcoin’s PoW). To merge mine a sidechain, a Bitcoin miner would run node software for the sidechain and configure it with their Bitcoin miner.
Merkle proof
A set of hashes that can be used to prove a given leaf's (i.e., a given piece of data) membership in a Merkle tree (i.e, a compressed data format).
Modular blockchain
A specialized blockchains that focuses on only one core function of a blockchain: consensus, security, data availability, or execution. This is similar to the microservices approach in software engineering, where each service is specialized in one function and can be swapped out for another service that performs the same function.
MPC (multi-marty computation) bridge
A cryptographic technique that enables a group of participants (a federation) to collectively manage and control the movement of BTC between Bitcoin and a given destination chain.
Multisig (multi-signature) wallet
A wallet for which at least two private keys are needed to sign a transaction.
O
Opcode (operation code)
An instruction in Bitcoin Script used to dictate logic for transactions, enabling the creation of custom transaction types and smart contracts. Bitcoin Script supports hundreds of opcodes which can be combined to create complex (but not Turing-complete) scripts that define the conditions under which a UTXO can be spent.
Optimium
A modular execution layer that has a canonical bridge contract with its underlying L1, but does not use that L1 for data availability. Fraud proofs are used to challenge invalid state transitions posted by the sequencer to the L1 contract. Unlike validiums, the enforcement of valid state transitions for optimiums relies on the ability of users to access data availability to create challenges.
P
Payment channel
A two-of-two multi-signature wallet that enables two parties to conduct limitless transactions between themselves without broadcasting each one to the Bitcoin network. Only the state differential (i.e., the start state and the end state) need to be posted onchain to close a payment channel and settle the balance.
Prover
A node actor in validity rollups systems which submits a SNARK proof that attests to the correctness of a rollup state transition. Rollup state transitions are considered final after the proof is accepted onchain, which also enables the corresponding bridge contract to process withdrawals.
Proof-of-Stake (PoS)
A sybil resistance mechanism in which the right to produce a block is proportional to an actor’s staked assets. PoS systems are designed to be more energy-efficient than PoW systems, as they do not require miners to solve complex mathematical puzzles to produce blocks. Instead, PoS systems rely on validators to propose and validate blocks based on the amount of assets they have staked as collateral. PoS systems typically use endogenous security resources.
Proof-of-Work (PoW)
A sybil resistance mechanism in which the right to produce a block is awarded to the actor that solves a computationally difficult problem, such as guessing the input to a hash function. PoW systems are designed to be energy-intensive and require miners to invest in specialized hardware to compete for block rewards. PoW systems typically use exogenous security resources. PoW systems are typically distributive for tokens, unlike PoS systems which are accumulative; this difference is due to the overhead costs of exogenous security resources.
R
Rollup
A modular blockchain that uses a parent blockchain for data availability. The blockchain stores its state root and enough transaction data to reconstruct the state of the blockchain from genesis in the parent blockchain.
S
Sequencer
A node actor that includes and orders transactions within rollup, or validia chain, blocks. These systems take transactions from the rollup mempool and construct blocks. These systems can range from being centralized servers or decentralized consensus networks.
Sidechain
An L1 that exists to add more functionality to BTC the asset. L1s are sovereign in technical architecture but typically exist as subsets of the broader Bitcoin ecosystem. It’s common for sidechains to enshrine a BTC bridge into their consensus mechanisms or involve Bitcoin miners in consensus - through merge mining or fee sharing.
Smart contract
A self-executing program that automates the actions required in a blockchain transaction. A smart contract is like a digital vending machine: a deterministic, transparent, and automated procedure.
Soft fork
A backward-compatible upgrade to a network's protocol that introduces new rules, allowing upgraded nodes to recognize and enforce these rules while non-upgraded nodes continue to operate under the old rules.
Sovereign rollup
A rollup implementation that sovereignly manages its own execution environment, and does not have a canonical bridge with its parent blockchain. Rollups on Bitcoin are technically sovereign rollups, even if they have a socially enshrined two-way peg.
Spiderchain
A sidechain protocol that leverages a variety of rotating multi-sigs to secure the BTC that is deposited into the sidechain.
State channel
A type of L2 scaling solution that allows participants to conduct transactions offchain, in a faster and cheaper environment. Only the state differentials (i.e., the start state and the end state) are recorded on the blockchain, reducing the load on the main network and by extension, the fees required. Unlike rollups, state channels do not have a 'global state' and instead exist as a series of bilateral agreements between participants.
State validation
A mechanism by which a blockchain is able to validate that a state transition (e.g., a transaction) was performed correctly.
Statechain
A protocol where users enter a 2-2 multisig with a federated entity and transfer ownership of a UTXO to an intended recipient by providing them a statechain private key for that specific UTXO.
Subnet
A specialized blockchain that operates within a larger network, designed to handle specific tasks or applications independently.
T
Two-way peg
A system that facilitates the minting and burning of BTC-backed tokens on a Bitcoin layer or alternative L1. These systems are also known as bridges.
U
Unilateral exit
The ability of a single participant to withdraw funds from a bridge without permission from any other network participant. In practice, unilateral exit often describes the ability to exit a bridge using an L1 transaction, providing a safeguard against bridge liveness and security failures.
Unspent Transaction Output (UTXO)
Bitcoin’s accounting model. A UTXO is an amount of BTC that has never been spent. UTXOs are ephemeral and can only be spent once. By spending a UTXO, it is destroyed and one or more UTXOs of equivalent value must be created in its place. UTXO creation and destruction exists in a many:many model, with multiple inputs and outputs allowed. This is in contrast to the account-based accounting model used by Ethereum, where balances are stored in accounts (i.e., a global state) and can be spent multiple times.
V
Validity rollup
A rollup where a prover submits a validity proof to a verifier contract on the L1 proving that the state transition was executed correctly.
Validia
A modular execution layer that has a canonical bridge contract with its underlying L1, but does not use that L1 for data availability (it instead uses an offchain system for data availability). Validia is a general term for validiums (validia using validity proofs) and optimiums (validia using fraud proofs).
Validity proof
A cryptographic proof that mathematically verifies the validity of an execution trace up front. Validity proofs ensure that a given state transition or set of transactions is valid according to the rules of the protocol immediately, unlike fraud proofs which optimistically assume correctness and rely on watchtowers to catch malicious actors after the fact.
Validium
A modular execution layer that has a canonical bridge contract with its underlying L1, but does not use that L1 for data availability. Validity proofs are used to prove the validity of state transitions posted to the L1 contract.