Architecture Lexicon

Web3 & Dime Network Glossary

A comprehensive reference index defining key technical concepts, consensus algorithms, cryptographic primitives, and execution primitives in high-throughput decentralized networks.

Futuristic digital archive and index with categorized glowing data tablets

Proof of History (PoH)

Consensus

A high-frequency Verifiable Delay Function (VDF) evaluated sequentially via SHA-256 hashes that provides an unforgeable cryptographic record of the passage of real time across distributed network nodes.

Architectural Context: Enables leader nodes to timestamp transactions before sending them to consensus, eliminating synchronous inter-node gossip delays for clock synchronization.

Tower BFT

Consensus

A custom Byzantine Fault Tolerant consensus algorithm optimized for Proof of History, utilizing exponential voting lockouts that increase as subsequent blocks are confirmed.

Architectural Context: When a validator votes on a fork, its commitment doubles with every subsequent block, reaching practical finality after 31 confirmation cycles.

Leader Schedule

Consensus

A deterministic schedule generated at the beginning of each epoch that assigns specific slots to validators proportionally weighted by their active delegated stake.

Architectural Context: Nodes know in advance which validator will produce blocks at any given millisecond slot, allowing direct packet routing via QUIC.

Slot & Epoch

Consensus

A slot is the fundamental unit of ledger time (nominally 400ms) during which a leader produces a block. An epoch is a collection of slots (typically 432,000 slots, ~2-3 days) where validator stakes and reward schedules are recalculated.

Architectural Context: Validator commission changes and stake delegation warmups/cooldowns only take effect at epoch boundaries.

Optimistic Confirmation

Consensus

A consensus state reached when at least two-thirds of the total active validator stake has voted on a given block, providing rapid assurance before full 31-slot root finality is reached.

Architectural Context: Allows applications and wallets to recognize transaction validity within ~400–800ms of broadcast.

Turbine

Networking

A multi-layer tree-based block propagation protocol that breaks blocks into small packets called shreds, utilizing Reed-Solomon erasure codes to broadcast data across large clusters with minimal leader bandwidth.

Architectural Context: A leader sends shreds to a small root fanout of nodes, which recursively forward shreds down tree levels, achieving sub-second global cluster saturation.

Gossip Protocol

Networking

An asynchronous peer-to-peer communication network where nodes periodically exchange network health, active node lists, and consensus votes over UDP sockets.

Architectural Context: Maintains cluster membership and liveness without requiring a centralized discovery registry.

TPU (Transaction Processing Unit)

Networking

The dedicated hardware and network pipeline on a validator node responsible for receiving inbound user transactions via QUIC, verifying signatures, and staging transactions into the execution engine.

Architectural Context: Consists of FetchStage, SigVerifyStage, BankingStage, and BroadcastStage running across dedicated CPU cores and GPU acceleration.

Shred & Erasure Coding

Networking

A fractional slice of a block payload. Leaders generate data shreds and parity (recovery) shreds using Reed-Solomon algorithms, allowing receiving nodes to reconstruct the complete block even if up to 33% of packets are lost in transit.

Architectural Context: Eliminates the need for expensive packet re-transmission requests across congested transatlantic network links.

Stake-Weighted QoS (SWQoS)

Networking

A traffic management policy that allocates TPU ingress bandwidth and transaction processing priority to RPC nodes and stakers proportionally to the amount of network stake they represent.

Architectural Context: Prevents network flooding and DDoS attacks by ensuring unstaked spam cannot crowd out legitimate validator and institutional transactions.

Sealevel Parallel Runtime

Execution

A multi-threaded smart contract execution engine that analyzes transaction read and write account access lists to process non-conflicting instructions simultaneously across all available CPU threads.

Architectural Context: If Transaction A modifies Account 1 and Transaction B modifies Account 2, both execute concurrently on separate CPU cores without serial locking.

Account Model & Owner Programs

Execution

All state in the network is stored inside discrete accounts. Each account contains a balance, a data byte vector, an executable flag, and an assigned owner program ID that possesses exclusive write authority over the account's data.

Architectural Context: A custom token contract owns all user token balance accounts; user keys only sign transfer authorizations.

Program Derived Address (PDA)

Execution

An off-curve public key generated deterministically from an owner Program ID and a set of seed strings. PDAs do not have corresponding private keys and can only be signed for by the owning program via runtime Cross-Program Invocations.

Architectural Context: Used extensively for escrow accounts, automated market maker pools, and state registry records.

Cross-Program Invocation (CPI)

Execution

A direct synchronous call made from one on-chain program to another during instruction execution, allowing composable smart contracts to pass signed privileges and invoke external logic.

Architectural Context: A lending contract calling the native Token Program to transfer collateral tokens into an escrow account.

Compute Units (CU) & Compute Budget

Execution

A measure of computational execution resources (CPU cycles, memory allocation, syscalls) consumed by a transaction. Each transaction specifies a maximum CU limit and priority fee rate per CU.

Architectural Context: Transactions that exceed their requested compute budget revert immediately, consuming the base fee to deter computational spam.

Ed25519 Cryptography

Security

A high-speed Edwards-curve Digital Signature Algorithm (EdDSA) utilizing Curve25519 that provides robust security against side-channel attacks and allows hardware-accelerated batch verification.

Architectural Context: Used for native keypair generation and transaction authorization signatures across validator and user accounts.

Seed Derivation & SLIP-0010

Security

Standardized hierarchical deterministic (HD) key derivation framework for Ed25519 curves based on BIP39 mnemonic phrases.

Architectural Context: Standard derivation path `m/44'/501'/0'/0'` ensures deterministic wallet address generation across compliant hardware and software signers.

Threshold Multisignature

Security

A cryptographic governance scheme requiring M valid signatures out of N designated authorized signers before an on-chain instruction (such as a program upgrade or treasury transfer) can be committed.

Architectural Context: A 3-of-5 multisig requires approval from at least three security officers before deploying smart contract code updates.

Slashing & Delinquency

Security

Penalties enforced against validators for malicious consensus behavior (such as producing conflicting blocks on two forks) or prolonged offline delinquency that degrades cluster finality.

Architectural Context: Protects network integrity by imposing economic consequences on compromised or misconfigured node operators.

Hardware Security Module (HSM)

Security

A dedicated physical computing device designed to securely store private cryptographic keys and perform onboard transaction signing without ever exposing the raw secret key to host memory.

Architectural Context: Validator operators connect remote signer daemons to HSMs to protect validator vote and identity keys against server compromise.

Rent & Rent Exemption

Storage

A storage fee mechanism where accounts must maintain a minimum balance proportional to their byte size. Accounts holding at least two years of rent fees are deemed 'rent exempt' and remain permanently in active RAM storage.

Architectural Context: When creating a new on-chain state account, the developer deposits ~0.002 units to achieve permanent rent exemption.

Cloudbreak / State Indexing

Storage

A memory-mapped file architecture optimized for concurrent reads and writes across solid-state drives, avoiding standard SQL or key-value storage bottlenecks.

Architectural Context: Enables validator nodes to query account states simultaneously across multiple NVMe storage arrays.

State Compression & Merkle Trees

Storage

A technique that stores large collections of data off-chain inside concurrent Merkle trees, writing only the root hash onto the blockchain to dramatically reduce on-chain storage costs.

Architectural Context: Allows millions of digital assets or state records to be minted and managed for a fraction of the cost of standard on-chain accounts.

Methodological Note on Network Terminology

The definitions compiled in this lexicon represent consensus engineering standards established across high-throughput distributed systems research. All entries are reviewed by our Bangkok research staff and updated periodically as protocol specifications evolve.

For comprehensive architectural walkthroughs of these primitives in action, refer to our Research Guides or explore our Educational Briefing Syllabus.