Glossary
Last updated
Last updated
An atomic transaction in the context of blockchain is a transaction composed of multiple interdependent actions, potentially across different chains or involving various smart contracts, that either executes in its entirety or is fully reverted. This ensures that no partial state changes occur, preserving the system's consistency. A key example of atomic transactions is atomic swaps, where tokenized assets are exchanged between different blockchains without third-party intermediaries. Atomic swaps leverage cryptographic mechanisms like Hash Timelock Contracts (HTLCs) to ensure that the swap is completed fully or canceled, maintaining decentralization and preventing any party from being shortchanged.
A consensus client in a blockchain node implements the network's consensus mechanism, ensuring that the blockchain reaches agreement on valid data by verifying the information provided by the execution client. It enables nodes to synchronize and maintain the correct blockchain state across the network.
Data availability refers to the guarantee that transaction data in a blockchain is published and accessible to all network participants for verification. It ensures that the data required to validate a blockchain’s state is publicly available, preventing malicious actors from withholding critical information while claiming valid execution.
An execution client in a blockchain node processes incoming transactions, executes them in the virtual machine, and maintains the current state and database of all network data. It is responsible for listening to new transactions and updating the blockchain's ledger accordingly.
An Indexed Merkle tree is a variant of the where each data element is associated with a specific index, enabling more efficient lookup and verification. This structure enhances data retrieval by ensuring that the position of each piece of data within the tree is explicitly defined, optimizing the process of generating proofs for individual elements.
A key-value store is a type of database that stores data as a collection of key-value pairs, where each key is unique and maps to a specific value. It allows for efficient retrieval of values based on their associated keys, commonly used in caching and simple data retrieval scenarios.
A Merkle tree is a cryptographic data structure that organizes data into a tree-like format, where each leaf node represents a hash of a data block, and each non-leaf node is a hash of its child nodes. This structure allows efficient and secure verification of large sets of data by providing a single root hash that represents the entire dataset, with proofs for individual data points requiring only a small portion of the tree.
A modular blockchain is a blockchain architecture that separates core functions such as execution, consensus, and data availability into specialized layers, allowing each layer to focus on one or more specific tasks. This modular approach enhances scalability, flexibility, and efficiency by enabling different blockchains to collaborate and optimize for specific roles, rather than handling all functions within a single, monolithic chain.
Restaking is a process where staked assets are reused to secure additional protocols or networks, enabling the same capital to generate multiple streams of rewards. This enhances capital efficiency by allowing staked assets to participate in various decentralized finance (DeFi) operations without requiring further investment or unstaking the original assets.
A session key in Web3 is a temporary, limited-permission credential that allows users or AI agents to perform specific transactions or actions on behalf of a primary account without requiring repeated wallet authentications. It consists of a signing key and a configuration that defines its permissions, such as asset usage, transaction limits, and expiration, enabling seamless interaction with decentralized applications while maintaining security.
Force inclusion is a mechanism in blockchain systems that allows users to bypass a malfunctioning or unresponsive Sequencer and ensure their transaction is included in the blockchain. After a predefined delay, any user can move their pending transaction from a secondary queue (like the delayed inbox) to the primary state-processing queue (the core inbox), ensuring censorship resistance and trustless inclusion even when the Sequencer fails to perform its duties.
In the case of a keystore rollup, this is structured as a . Specifically, an , which optimizes for its access purpose.
A light node is a type of blockchain node that only downloads and verifies block headers rather than the full blockchain, allowing it to operate with minimal resource requirements. By requesting additional data from full nodes (or its modular components such as layer) when needed and verifying it against the block headers, light nodes provide access to the blockchain's functionality and security guarantees without the need for powerful hardware, making them suitable for lightweight devices and specialized networks like keystores.