Dime Technical Glossary & Architecture Directory

Comprehensive Technical Glossary

Welcome to the Dime Technical Glossary & Architecture Directory. This educational reference defines key terminology across distributed ledger architecture, validator operations, consensus mathematics, and cryptographic key security in clear, accessible language.

Category 1: Foundational & Protocol Concepts

1. Account Model

The database architecture used by Dime where state is stored in independent memory buffers identified by 32-byte public keys. Unlike Bitcoin’s UTXO model, accounts separate executable code (programs) from mutable data balances.

2. Slot

A fixed duration of time (approximately 400 milliseconds) during which a designated Leader Validator is authorized to ingest transactions and propose a new block to the network.

3. Epoch

A predetermined sequence of consecutive slots (typically 432,000 slots, or roughly 2 to 3 days). At epoch boundaries, leader schedules are regenerated and validator stake distributions are updated.

4. Verifiable Delay Function (VDF)

A cryptographic computation that requires a fixed, sequential number of sequential steps to evaluate, creating an unforgeable, deterministic passage of time within the distributed network ledger.

5. Instruction

The basic atomic execution unit in a Dime transaction. An instruction specifies which program to invoke, which accounts to pass as arguments, and an arbitrary byte array of operational input data.

6. Transaction Processing Unit (TPU)

The multi-threaded processing pipeline within a validator node that ingests incoming network transactions, verifies signatures, executes state transitions in parallel, and packages shreds for broadcast.

Category 2: Validators & Consensus Mechanics

7. Byzantine Fault Tolerance (BFT)

The ability of a distributed computing network to function correctly and reach consensus even when some peer nodes fail, drop packets, or broadcast deliberately malicious data, as long as malicious actors control less than one-third of voting weight.

8. Leader Validator

The validator node designated by the deterministic leader schedule to author and broadcast the next proposed block for a specific slot window.

9. Sentry Node Architecture

A defensive network setup where a private, high-security validator node is isolated behind a cluster of public-facing proxy nodes (sentries) to protect the core signing node from DDoS attacks.

10. Turbine

A high-throughput block propagation protocol that breaks large blocks into smaller erasure-coded chunks (shreds) and distributes them across a hierarchical tree of validator nodes, preventing leader bandwidth saturation.

11. Slashing

An automated protocol penalty enforced against validator nodes that commit safety violations—such as double-signing two conflicting blocks for the same slot.

12. Root Slot

The latest block height in the ledger that has received supermajority confirmation ($> 66.6%$) and is considered permanently immutable and finalized.

Category 3: Wallet, Keys & Defensive Security

13. Asymmetric Key Pair

A mathematical pair of cryptographic keys consisting of a public key (used as a receiving address and signature verification key) and a private key (used to sign transactions and authorize state changes).

14. Ed25519

A high-performance elliptic curve signature algorithm based on twisted Edwards curves, offering constant-time execution, fast signature verification, and strong resistance to side-channel attacks.

15. BIP-39 Mnemonic Phrase

A standardized list of 12 or 24 English words generated from high-entropy cryptographic randomness that allows users to backup and restore an entire hierarchy of private keys.

16. Hardware Security Module (HSM)

A physical computing device engineered with tamper-resistant secure elements that securely generates, stores, and executes cryptographic signatures without exposing private keys to the host operating system.

17. Multi-Signature (Multisig)

A security architecture requiring approvals from a specified threshold ($m$-of-$n$) of independent cryptographic signers before a transaction can be executed.

18. Air-Gapped Signing

A defensive operational practice where transaction payloads are created on an internet-connected computer and transferred via QR code or physical USB drive to an offline, non-networked device for cryptographic signing.

Category 4: Developer Ecosystem & Telemetry

19. JSON-RPC Gateway

A standard communication interface allowing web applications and external tools to query blockchain state and dispatch transactions over HTTP/HTTPS and WebSockets.

20. Geyser Plugin

A low-latency C/Rust dynamic library plugin interface embedded inside validator software that streams real-time state changes directly to external databases and messaging queues.

21. Prometheus Exporter

A background daemon that collects operational metrics (CPU load, memory allocations, slot latency, peer count) from a validator node and exposes them for scraping by time-series monitoring engines.

22. eBPF (Extended Berkeley Packet Filter)

A sandboxed bytecode architecture and virtual machine runtime used by Dime to execute compiled smart contract instructions safely and with minimal execution overhead.

23. Rent Exemption

A protocol mechanism where accounts holding a minimum balance proportional to their byte storage size are exempt from periodic storage fees, ensuring long-term ledger sustainability.

24. Transaction Simulation

An RPC endpoint capability that executes a proposed transaction against the current state in a dry-run environment, returning execution logs and potential errors without committing on-chain mutations.