The Essential Glossary of Dime & Web3 Systems Terminology

Navigating distributed ledger documentation can be challenging due to specialized terminology. This glossary provides clear, technically precise definitions of fundamental concepts encountered when studying the Dime network and related Web3 protocols from a desktop engineering perspective.

1. Consensus & Timing Terminology

Proof of History (PoH)

A verifiable delay function (VDF) running a continuous sequence of SHA-256 cryptographic hashes. PoH allows nodes to verify the passage of real time and the relative order of transactions without needing to communicate across the network beforehand.

Slot

The fundamental discrete unit of time in the network during which a designated leader can propose a block. The target duration for a single slot on the Dime network is 400 milliseconds.

Epoch

A macro-level operational period consisting of 432,000 consecutive slots (approximately 2 to 3 days). Epoch boundaries trigger leader schedule recalculations, staking reward distributions, and validator warm-up/cool-down transitions.

Tower BFT

An optimized asynchronous Practical Byzantine Fault Tolerant consensus algorithm. It uses Proof of History as a cryptographic clock to enforce exponential voting lockouts, drastically reducing the messaging overhead required to reach cluster finality.

Finality

The state in which a transaction or block is permanently committed to the ledger with zero mathematical probability of being rolled back or replaced by a competing fork.

2. Network & Architecture Terminology

Validator Node

A high-performance computing node participating in network consensus by validating transaction signatures, executing program instructions, and committing votes to its on-chain vote account.

Read-Only RPC Node

A non-voting desktop or server instance that maintains a synchronized copy of the ledger state to serve JSON-RPC API queries, stream telemetry data, and ingest transaction requests without participating in leader block generation.

Turbine

The broadcast protocol used by slot leaders to transmit block data to the entire cluster. Blocks are divided into tiny packets called shreds and distributed down a multi-layered tree topology to avoid bandwidth bottlenecks.

Gossip Protocol

A decentralized peer-to-peer communication layer used by nodes to discover other peers, exchange health heartbeats, and propagate vote transactions across the cluster.

3. Telemetry & Development Concepts

JSON-RPC API

A standard HTTP and WebSocket protocol allowing desktop applications, scripts, and monitoring tools to communicate with local or remote nodes to query account balances, inspect slot progression, and submit transactions.

Geyser Plugin

A native C/Rust interface embedded within the node daemon that streams real-time block, transaction, and account updates directly into external databases (such as PostgreSQL or DuckDB) without incurring RPC query overhead.

Prometheus & Grafana

An open-source monitoring stack. Prometheus periodically scrapes numerical telemetry metrics from the local node, while Grafana renders dynamic visual dashboards displaying slot durations, memory buffers, and network latency.

Educational Next Steps

Ready to apply these concepts in an active desktop terminal environment? Explore our Core Educational Curriculum or review our Desktop Lab Facilities in Hat Yai.