Skip to content

QF Glossary

This glossary contains terms that are actively implemented and used within the QF Network ecosystem. These terms represent the core components, technologies, and concepts that make up the current QF Network implementation.

A

Accelerator

Consensus

A designated special player responsible for fast transaction confirmations during optimistic scenarios.

Comment: Similar to the Leader in SPIN consensus

Anchor Chain

Consensus

High-value PoS network (like Polkadot) that validates and finalizes Fast Chain proofs to provide additional security guarantees.

Comment: Provides second-tier finality for Fast Chain blocks. Previously called "slow chain" (same as in Thunderella paper) and "Relay Chain" in early drafts

Archive node

Node Types

A node that stores a complete record of states for every block and the entire blockchain history.

Comment: Final source of truth Used for verification the balance of a specific account for a specific time

Authority-based round-robin scheduling (AURA)

Consensus

Provides a slot-based block authoring mechanism, where a known set of authorities take turns producing blocks.

Comment: Used in some Polkadot SDK-based (ex Substrate) chains. One of the potential base consensus options for QF Network's SPIN implementation.

B

B_heartbeat_interval

SPIN Parameters

Number of blocks between leader liveness heartbeats sent to parachain

Comment: Ensures leader availability monitoring

B_recovery_delay

SPIN Parameters

Number of parachain blocks after the last FCFP before the parachain initiates Finality Recovery Mode.

Comment: Controls when recovery mode triggers due to missing FCFPs.

B_recovery_duration

SPIN Parameters

Number of parachain blocks that Finality Recovery Mode continues before transitioning back to operational mode.

Comment: Controls duration of recovery procedures.

BLAKE3

Cryptography

High-performance cryptographic hash function used as universal hashing primitive in QF Network

Comment: Replaces default Polkadot SDK (ex Substrate) hash functions for performance optimization

Blind Assignment for Blockchain Extension (BABE)

Consensus

Polkadot's block production mechanism

Comment: Used in some Polkadot SDK-based (ex Substrate) chains. One of the potential base consensus options for QF Network's SPIN implementation.

Blob

Storage

Binary data stored on the blockchain, particularly in smart contract context.

Comment: Used in PolkaVM for smart contract code storage, e.g. https://github.com/QuantumFusion-network/spec/blob/main/docs/PolkaVM/blob_hashing_addressing.md

Block

Core terms

A collection of data, such as transactions, that together indicate a state transition of the blockchain.

Comment: Typically contains: transaction data, hash, previous block hash, validator information

Block Batch

Consensus

Set of Fast Chain finalized blocks submitted to Anchor Chain in one transaction through the Bridging Gadget.

Comment: Reduces overhead by batching multiple blocks for Anchor Chain validation.

Block Explorer

User Interface

A web tool for inspecting and navigating detailed blockchain data, including blocks, transactions, addresses, and smart contracts.

Comment: Part of portal. Contains block viewer Examples: https://etherscan.io, https://subscan.io More focused than a portal but more comprehensive than a block viewer. Block explorers provide search functionality and detailed transaction data.

Block Viewer

User Interface

A simplified interface specifically for viewing basic block data and recent transactions without the additional analysis features of a full explorer.

Comment: Part of block explorer (part of portal) Examples: https://blockchair.com/bitcoin/blocks, https://www.blockchain.com/explorer/blocks/btc The simplest of the three interfaces. Block viewers show core blockchain activity with minimal complexity.

Blockchain

Core terms

A distributed ledger technology that maintains a continuously growing list of records (blocks) secured using cryptography.

Blockchain Trilemma

Core terms

A well-known problem in blockchain design asserting that a decentralized system can only achieve two out of three properties: decentralization, security, and scalability. SPIN's hybrid consensus aims to mitigate this by allowing fast, scalable networks to inherit security from larger, established chains

Bootnode

Node Types

Initial node that helps others connect to the network.

Comment: Used during peer discovery.

Bridging Gadget

Consensus

Finite State Machine executed on Anchor Chain that validates Fast Chain Finality Proofs and manages recovery procedures.

Comment: Core component enabling SPIN's hybrid consensus. Implemented as custom parachain runtime on Polkadot Relaychain.

Bridging Gadget Operators

Consensus

Validators responsible for operating the Bridging Gadget, submitting FCFPs to the Anchor Chain, and managing cross-chain communication.

Comment: In SPIN, the Operators Set equals the Validators Set for simplicity. Rotation not tied to Primary Leader Tenure. Previously called "Collation Leader" in older drafts.

Bulk Coretime

Core terms

A purchasing model for parachain slots on Polkadot using bulk time allocation.

C

Cap'n Proto

Infrastructure

High-performance RPC serialization protocol with zero-copy decoding and promise pipelining

Comment: Used for QF Network's RPC layer to achieve sub-100ms response times

Chain Growth

Consensus

Ensures the blockchain grows steadily over time, within defined bounds.

Chain Quality

Consensus

Minimum portion of blocks from honest nodes.

Comment: Ensures integrity under partial corruption.

Chopsticks

Development

A mechanism for creating a test environment on Polkadot SDK (ex Substrate) (similar to a sandbox) for sending transactions via RPC

Comment: Used for test execution before network deployment.

Collator

Node Types

Type of node (typically near full node) in the parachain Polkadot SDK-based (ex Substrate) network. Responsible for validating, block production, pre-finalization of blocks and communication with relay chain (for example with validators).

Comment: Collects parachain transactions and produces state transition proofs (Proof-of-Validity, PoV) for the validators. In the context of SPIN, Fast Chain Validators also serve as Collators (specifically, as Bridging Gadget Operators) to carry out information relaying duties and submit information to the Anchor Chain

Committee

Consensus

A predefined subset of nodes tasked with verifying transactions rapidly in cooperation with the Leader

Comment: Works with Leader (Accelerator) for quick notarization.

Common Prefix

Consensus

A consistency property: the chain of an honest node is a prefix of any other honest node's chain.

Consensus

Core terms

The process by which network participants agree on the state of the blockchain

Comment: Ensures all nodes have a consistent view of the ledger, securing the system against fraud and discrepancies.

Consistency, Availability, and Partition Tolerance (CAP theorem)

Core terms

Theorem states that a distributed data store can only provide two out of the following three guarantees simultaneously: Consistency, Availability, and Partition Tolerance.

contracts-ui

Development

Web interface for deploying and interacting with smart contracts

Comment: Adapted for QF Network smart contract interaction

Coretime

Core terms

Scheduled execution time on Polkadot for parachains.

D

Dashboard

User Interface

Visual overview of network performance, blocks, and usage.

Comment: Supports validators and telemetry

decentralized Application (dApp)

Development UI

Application that interacts with a blockchain using RPC to read data and a wallet to write to the blockchain.

Comment: Frontend integrates with smart contracts.

DevNet

Core terms

A development network environment for early testing of blockchain functionality before TestNet deployment.

Comment: Demonstrating core functionality with a small number of validator nodes.

E

EcoSystem

Core terms

The complete environment of interconnected applications, services, and components that make up the blockchain network.

Election Finalization Block

Consensus

Specific block where validator election results are determined and finalized, occurring after the Last Voting Block.

Comment: Either accepts off-chain Phragmen solutions or triggers on-chain calculation by Primary Leader.

Epoch

Consensus

A block production period with pre-known starting time and fixed-length during which the set of block producers stays constant. Epochs are indexed sequentially and divided into equal-length periods known as block production slots. Each slot is awarded to a subset of block producers during which they are allowed to generate a block. Governance, nomination, and validator selection processes occur within epoch boundaries to determine the validator set for subsequent epochs.

Comment: Detailed mechanics in older drafts.

Extrinsic

Development

Extrinsics are transactions that originate outside of the blockchain runtime. They are calls to functions within functional pallets on the blockchain and can be executed successfully, provided the caller has the necessary permissions.

Comment: The mechanism for submitting operations

F

Fast Chain

Consensus

QF Network's main blockchain with 100ms target block time that processes normal transactions and maintains sovereignty while anchoring to Polkadot.

Comment: The primary chain users interact with, enhanced with additional security from Anchor Chain.

Fast Chain Finality Proof (FCFP)

Consensus

Cryptographic proof consisting of block hash signed by majority of Fast Chain Validators, submitted to Anchor Chain for validation.

Comment: Core mechanism for transferring finality from Fast Chain to Anchor Chain.

Fast Chain Nominations Proof (FCNP)

Consensus

Cryptographic proof containing sufficient data for verifying Fast Chain nominations changes.

Comment: Used during validator set elections to prove nomination validity.

Fast Chain Validator Set Proof (FCVSP)

Consensus

Cryptographic proof containing sufficient data for verifying Fast Chain validator set changes.

Comment: Enables Anchor Chain to verify validator set elections and rotations.

Fast Path

Consensus

An optimistic execution path where transactions are instantly confirmed through the cooperation of the Leader (accelerator) and Committee without waiting for standard blockchain delays.

Faucet

Development UI

A service that distributes test tokens to users on DevNet or TestNet

Comment: Allows developers to obtain tokens for testing without purchasing or mining. Repo: https://github.com/QuantumFusion-network/devnet-faucet

FCFP Block

Consensus

A block whose hash and finality justifications are included in a Fast Chain Finality Proof.

Comment: The specific block being proven to the Anchor Chain.

FCFP Tail

Consensus

Sequence of blocks covered by a single FCFP, from the FCFP Block back to the previous FCFP Block.

Comment: Defines the scope of blocks validated in each proof submission.

FCFP Transaction

Consensus

Transaction submitted to Bridging Gadget containing FCFP along with block batch headers.

Comment: Primary mechanism for transferring finality information from Fast Chain to parachain.

Finality Recovery Mode

Consensus

Emergency procedure activated when Fast Chain finality stalls, using Anchor Chain to restore consensus and elect new Primary Leader.

Comment: Ensures liveness even when Fast Chain consensus fails. Detailed procedures in older drafts. Secondary Leaders produce operational-only blocks during recovery.

Finalized Block

Core terms

A block that has been accepted as canonical and will not be reverted.

Comment: Used in finality (e.g. GRANDPA).

Forkless Runtime Upgrades

Architecture

A mechanism to update blockchain logic without requiring hard forks.

Comment: Inherited from Polkadot SDK (ex Substrate)

Framework for Runtime Aggregation of Modularized Entities (FRAME)

Development

A system for building pallets in Polkadot SDK (ex Substrate).

Full node

Node Types

A node that stores the entire blockchain history and current state, validates transactions and blocks.

Comment: Serves as the final source of truth in the network, executes transactions, and provides Merkle proofs to light nodes.

G

Gas

Transactions

A fee or cost required to conduct a transaction on the blockchain, denominated in small fractions of cryptocurrency

Comment: If the transaction fails, the gas will be debited, but the transaction will have to be restarted and the gas will have to be paid for again.

Gas limit

Transactions

The maximum price a cryptocurrency user is willing to pay when sending a transaction, or performing a smart contract function.

Gas Metering

Transactions

System for measuring and limiting computational resources used by transactions or smart contracts.

Genesis Block

Core terms

The first block of the blockchain from which all subsequent blocks build.

GHOST-based Recursive Ancestor Deriving Prefix Agreement (GRANDPA)

Consensus

A finality gadget for blockchain consensus.

Comment: A finality gadget used in blockchain consensus. In the SPIN protocol, it serves as one of the potential asynchronous finality methods for the Fast Chain and is used in the Relay Chain for finality validation

Gossip Protocol

Protocol

Propagation method for node-to-node communication.

Comment: Used in libp2p

Graceful Degradation

Consensus

Ensures system performance transitions smoothly from an optimal fast path to a slower consensus mechanism without failure.

H

HashDB

Storage

An interface for accessing blockchain state similar to a key-value store.

Comment: Part of QF Network's state storage optimization.

History

Storage

Chronological sequence of confirmed blocks and finalized states.

Comment: Typicaly retained via Archive Nodes and used in sync and audit logic

I

Inclusion Proof

Consensus

Cryptographic proof showing that a specific transaction was included in a finalized Fast Chain block.

Comment: Generated by Primary Leader in response to Yell Queries to prove transaction inclusion.

Instant Confirmation

Consensus

The capability to confirm transactions almost immediately (within network delay bounds) under optimistic conditions.

iroh

Storage

Distributed storage system for content-addressable data.

K

Key Management

Development

Tools and practices for managing cryptographic keys.

L

Last Voting Block

Consensus

Designated block after which no more validator candidate intentions or nominator votes can be submitted during an epoch.

Comment: Marks deadline for election participation before vote tallying begins.

Layer 1 (L1)

Core terms

The base layer of blockchain architecture that includes data storage, transaction processing, consensus, and RPC.

Comment: Parachain on Polkadot

libp2p

Infrastructure

A modular network framework used in blockchain systems for peer-to-peer networking.

Comment: Handles messaging and peer discovery.

Light Client

Node Types

A blockchain client that stores minimal data and relies on full nodes for verification.

Comment: Enables mobile support.

Light node

Node Types

A node that stores only part of the blockchain state and verifies data using full nodes.

Comment: Similar for Light Client. Included by default in user apps, can run transactions but has limited storage requirements.

Log-Structured Merge Tree (LSM tree)

Storage

Data structure that is optimized for write-heavy workloads.

Comment: Used in PolkaVM. Works by collecting writes in memory and periodically merging them into larger, on-disk structures.

M

MainNet

Core terms

The production blockchain network where real-value transactions occur.

Merkle Proof

Storage

Cryptographic verification mechanism that allows light nodes to verify data without storing the entire blockchain.

Comment: Enables light clients.

Merkle Tree

Storage

A tree data structure where every leaf node is labeled with the cryptographic hash of a data block, and every non-leaf node is labeled with the hash of its child nodes.

Comment: Used for efficient and secure verification of large data structures.

Metadata

Core terms

Data that includes information about other data, such as information about a specific transaction.

Metric(s)

Development

Quantifiable measurements used to track and assess the status of specific processes in the blockchain.

Comment: Includes block time, TPS, forks, etc.

Mode Switch Proof

Consensus

Fast Chain transaction proving recent mode change (recovery/operational) in the parachain, containing mode value and parachain finality proof.

Comment: Enables Fast Chain to track and respond to parachain state changes.

N

N_slashing

SPIN Parameters

Percentage of stake slashed for proven censorship or malicious behavior by validators.

Comment: Economic penalty for protocol violations.

N_validators_max

SPIN Parameters

Maximum number of validators allowed in the active set

Comment: Upper bound for validator set scaling

N_validators_min

SPIN Parameters

Minimum number of validators required for secure network operation.

Comment: Safety threshold for validator set size.

N_validators_quorum

SPIN Parameters

Percentage of validators required to validate and finalize blocks.

Comment: Consensus threshold for block finalization.

Node (as blockchain node)

Node Types

A machine running the blockchain engine, which can store blocks and participate in the network.

Comment: Has properties related to data storage, transaction capabilities, consensus participation, and RPC provision.

Node (as network node)

Core terms

A node that participates in network exchange, for example, a seed server

NOISE

Security

Cryptographic protocol framework for secure key exchange without centralized certificate authorities

Comment: Used with nQUIC for node-to-node encryption

Nominated Proof of Stake (NPoS)

Consensus

A consensus mechanism where network participants (nominators) delegate their stake to trusted validator nodes.

Comment: Validators are selected based on both their own stake and the stakes they receive from nominators. QF Network, which is built using the SPIN consensus, uses a derivative of Phragmen for NPoS to elect and prove its Validator Set selection

Normal Transactions

Consensus

All blockchain transactions excluding operational transactions - regular user and smart contract transactions.

Comment: Only processed by Primary Leader during normal operation, excluded during Secondary Leader block production.

nQUIC

Infrastructure

A modified version of the QUIC protocol using the NOISE protocol for key exchange.

Comment: Used for efficient, low-latency node-to-node communication.

O

Operational Transactions

Consensus

Blockchain transactions required for maintaining network operation, such as consensus messages and validator updates.

Comment: Can be processed by Secondary Leaders during recovery to maintain chain liveness.

Optimistic Conditions

Consensus

Conditions where the leader is honest and available, and a large fraction of nodes are correct, enabling fast-path confirmation.

Optimistic Responsiveness

Consensus

Confirms transactions as fast as the actual message delay in the network, assuming a supermajority of honest players and an honest accelerator.

Orphaned Block

Core terms

A block that has not reached finalization.

Comment: Transactions from orphaned blocks are typically taken and included in new blocks for finalization.

P

Pallet

Development

Modular component in Polkadot SDK (ex Substrate) that implements specific blockchain functionality.

Comment: Used for functionality like balances, assets, and consensus.

Parachain

Core terms

A specialized blockchain that runs in parallel to Polkadot's Relay Chain, sharing its security and interoperability features

Comment: QF Network operates as a parachain on Polkadot, inheriting its security model while maintaining sovereignty

Pessimistic Conditions

Consensus

Conditions under which optimistic assumptions fail, causing the protocol to fall back to slower consensus.

Comment: Triggers recovery mode.

PolkaVM

Development

A smart contract execution environment based on the RISC-V instruction set.

Comment: An advanced smart contract platform designed for high performance and EVM compatibility.

Portal

User Interface

A comprehensive web interface for interacting with a blockchain network that combines multiple tools including block exploration, wallet connectivity, network statistics, and developer tools.

Comment: A portal is the broadest interface type, providing a complete ecosystem entry point. A portal typicaly includes block explorer functionality, wallet connections, network monitoring, and developer tools in one unified interface.

Precompile

Development

Built-in functions in blockchain runtime that execute at near-native speed.

Comment: Used for frequently needed operations like cryptographic functions.

Primary Leader

Consensus

Designated Fast Chain validator responsible for producing blocks with normal transactions during assigned tenure.

Comment: Selected deterministically from validator set. Can be challenged through Yell Query mechanisms.

ProofStorage

Storage

A mechanism for generating Merkle proofs from blockchain state.

Comment: Enables light client sync.

Pruning Node

Node Types

A node that discards older blocks to save storage space while maintaining current state.

Comment: Will be implemented in a future phase when accelerated sync through checkpoints becomes available.

Q

QMDB

Storage

An embedded key-value store designed specifically for storing Merkelized data in the blockchain context.

Comment: Optimized for Merkle storage.

R

R_bridging_missed

SPIN Parameters

Ratio of slots missed by the Bridging Gadget Operator during an Epoch, calculated as missed slots divided by total slots.

Comment: Performance metric for leader accountability. Previously uses "Collation Leader" in older drafts.

R_bridging_missed_max

SPIN Parameters

Maximum allowed ratio of missed slots before Bridging Gadget Operator is penalized and disabled in the next epoch.

Comment: Threshold for leader performance penalties. Previously uses "Collation Leader" in older drafts.

Relay Chain

Core terms

Polkadot's central blockchain that coordinates the network, provides shared security, and enables communication between parachains.

Comment: Provides security and finality services to QF Network as a parachain. In SPIN context, serves as the Anchor Chain.

Remote Procedure Call (RPC)

Core terms

A software communication protocol that enables a program to facilitate the execution of a specific procedure on a different blockchain network.

Comment: Examples of RPC frameworks or formats: - JSON-RPC (JavaScript Object Notation Remote Procedure Call) - gRPC - Cap'n Proto

RocksDB

Storage

High-performance embedded database for key-value storage

Comment: Baseline storage engine being optimized/replaced in QF Network

RPC Layer

Infrastructure

The communication protocol layer that enables applications to interact with the blockchain through standardized methods.

Runtime

Core terms

The core logic of a blockchain that defines its state transition function.

Comment: It defines a valid algorithm for determining the state of the next block given the previous state. Can be upgraded through forkless upgrades. Defined by FRAME modules.

S

S_batch_size

SPIN Parameters

Number of Fast Chain blocks included in a single FCFP before submission to Bridging Gadget.

Comment: Controls batching efficiency for cross-chain proofs.

S_checkpoint_interval

SPIN Parameters

Number of blocks between state checkpoints for fast synchronization

Comment: Enables rapid node sync without full history replay

S_election_finalization

SPIN Parameters

Number of blocks before epoch end when validator election results must be finalized.

Comment: Deadline for completing validator elections.

S_epoch_duration

SPIN Parameters

Duration between validator set elections, encompassing the full governance and nomination cycle.

Comment: Fundamental timing for governance cycles.

S_fc_block_time

SPIN Parameters

Target time between blocks during normal operation on Fast Chain, currently set to 100ms.

Comment: Core performance target for Fast Chain block production.

S_last_voting_block

SPIN Parameters

Number of blocks before epoch end after which no more nominator votes are accepted.

Comment: Voting deadline for validator elections.

S_secondary_delay

SPIN Parameters

Number of consecutive slots the Primary Leader may miss before the Secondary Leader starts block production.

Comment: Core timing parameter for leader failover mechanism and Finality Recovery Mode activation.

S_tenure_duration

SPIN Parameters

Duration for which a single Primary Leader produces blocks before rotation to the next validator.

Comment: Leadership rotation timing to balance performance and decentralization.

S_witness_delay

SPIN Parameters

Time allocated for validators to submit witness messages during Finality Recovery Mode.

Comment: Timeout for accountability messages during recovery.

S_yell_response_delay

SPIN Parameters

Number of slots validators wait for the Primary Leader to include Yell Query transaction and provide inclusion proof.

Comment: Core anti-censorship timing parameter.

S_yell_user_delay

SPIN Parameters

Number of slots user waits before submitting Yell Query, noted as unused due to mempool visibility subjectivity.

Comment: Deprecated parameter, replaced by parachain fee mechanism.

Secondary Leader

Consensus

Backup block producer that activates when Primary Leader fails, maintaining chain liveness during recovery procedures.

Comment: Maintains network operation during Primary Leader failure. Detailed ranking system in older drafts.

Self-Consistency

Consensus

A node's chain does not contradict its own previous chain at any later point.

Comment: Used for validator safety.

Short-term Parallel Incremental Network agreement (SPIN)

Consensus

QF Network's custom consensus mechanism.

Simple Concatenated Aggregate Little-Endian encoding (SCALE)

Infrastructure

Simple Concatenated Aggregate Little-Endian encoding, used for efficient blockchain data serialization.

Slow Path (Fallback)

Consensus

A fallback mechanism that activates if the accelerator misbehaves or is unresponsive. Reverts to a slower, standard blockchain consensus process.

Comment: Triggers view change.

SmartContract

Development

Self-executing contract with terms directly written into code, running on a blockchain.

Smoldot

Development

Lightweight blockchain client implementation that can run in browsers and resource-constrained environments

Comment: Core component for QF Network light client support

sp-trie

Storage

Polkadot SDK (ex Substrate)'s implementation of Patricia Merkle Tree for state storage

Comment: Being replaced by QMDB in QF Network optimization efforts

Squid SDK

Development

Blockchain indexing framework for building APIs and explorers

Comment: Used for QF Network block explorer backend

State

Storage

Current snapshot of the network at a particular point in time, including information about accounts, balances, and other relevant data.

Comment: Each state has a hash (Merkle Proof). Includes transaction storage and global state of all blockchain.

State Machine Replication (SMR)

Consensus

A distributed systems abstraction where nodes agree on an ever-growing ordered log of commands.

State Root

Core terms

Hash of the entire blockchain state, stored in block headers.

Comment: Enables efficient proof verification.

Storage

Uncategorized

General term for how data is saved, managed, and accessed within the network.

T

Telemetry

Core terms

System for collecting and visualizing blockchain node metrics.

Tenure

Consensus

Fixed time period during which a single Primary Leader produces blocks before rotation to next validator.

Comment: Longer than individual block times to reduce network overhead while maintaining decentralization.

TestNet

Core terms

A more mature test network that replicates MainNet conditions, used for final testing before production deployment.

Comment: Mirrors production logic.

Transaction (TX)

Transactions

A record of a transfer of value from one account to another, stored in a block and validated by the network.

Comment: Transactions for execution are ranked based on gas price/CPU cycle Custom transactions in Polkadot SDK (ex Substrate) – a democratic discussion on proposing a new runtime

Turing-complete

Core terms

A system or language capable of performing any computation that a Turing machine can.

Comment: In the context of SPIN, the Turing-completeness of the Anchor Chain is a vital property. This allows for the execution of complex smart contracts, which is essential for implementing the Bridging Gadget and enabling advanced recovery procedures. SPIN drafts also noted the "Turing-complete flexibility of our Anchor chain" as a factor in handling errors

V

Validator node

Node Types

A network participant responsible for validating and proposing new blocks based on staked assets and delegated stakes.

Comment: Participates in consensus to propose and finalize blocks. Can use goodwill - a return mechanism if the sender makes a mistake and confuses gas values with money for a transfer

Verifiable Offchain Workers

Architecture

System that handles complex computations outside the blockchain with cryptographic proof of correct execution.

Comment: Enables support compute-intensive operations while maintaining fast block times.

View Change

Consensus

A process triggered when participants detect that the current accelerator is malicious, slow, or unavailable. Elects a new accelerator.

Comment: Similar to leader rotation in SPIN consensus.

W

Wallet

User Interface

Software that stores private keys, displays account balances, and enables transaction signing.

Comment: Stores cryptographic keys, queries node for account information, and generates transaction signatures.

WebRTC

Infrastructure

Web Real-Time Communication, a collection of protocols and APIs for direct browser-to-browser communication.

Comment: Used for peer-to-peer connections between browsers and blockchain nodes.

Witness Message

Consensus

Message submitted by validators during Finality Recovery Mode containing the latest finalized block hash produced by Primary Leader.

Comment: Used for accountability - validators failing to submit are disabled by next Primary Leader.

Write-Ahead Logging (WAL)

Storage

A technique that ensures data integrity by recording changes to a log before applying them to the ledger.

Comment: Allows the system to recover to a consistent state in case of failures.

X

XCM

Infrastructure

Cross-Consensus Message Format for communication between different consensus systems.

Comment: Used for integration with the Polkadot ecosystem.

Y

Yell Query

Consensus

Anti-censorship mechanism allowing users to submit transactions to Bridging Gadget when they suspect Fast Chain censorship.

Comment: Forces Primary Leader to provide Inclusion Proof or triggers Finality Recovery Mode. More details in older drafts.

Yell Target Transaction (YTT)

Consensus

Specific transaction that user believes is being censored by Primary Leader, referenced in Yell Query.

Comment: Must be included by Primary Leader with Inclusion Proof or triggers recovery procedures.

Z

zkTLS

Security

Zero-knowledge Transport Layer Security, a mechanism to securely attest Web2 data on-chain.

Comment: Used to bring Web2 data onto the blockchain in a verifiable way.