The persistent storage layer for all Solana accounts. AccountsDB stores account data in memory-mapped AppendVec files, indexed by pubkey and slot. It supports fast lookups, handles account deduplication across slots, and periodically cleans up dead accounts. AccountsDB is the largest consumer of validator disk space.
Empieza por la explicación más corta y útil antes de profundizar.
The persistent storage layer for all Solana accounts. AccountsDB stores account data in memory-mapped AppendVec files, indexed by pubkey and slot. It supports fast lookups, handles account deduplication across slots, and periodically cleans up dead accounts. AccountsDB is the largest consumer of validator disk space.
Usa primero la analogía corta para razonar mejor sobre el término cuando aparezca en código, docs o prompts.
Piensa en esto como parte del engranaje que mantiene funcionando el orden, la ejecución o el consenso de la red.
Ubica el término dentro de la capa de Solana en la que vive para razonar mejor sobre él.
Consenso, rotación de líderes, slots, epochs y el runtime.
Convierte el término de vocabulario en algo operacional para producto e ingeniería.
Este término desbloquea conceptos adyacentes rápido, así que funciona mejor cuando lo tratas como un punto de conexión y no como una definición aislada.
Usa este bloque compacto cuando quieras dar contexto sólido a un agente o asistente sin volcar toda la página.
AccountsDB (accounts-db) Categoría: Protocolo Base Definición: The persistent storage layer for all Solana accounts. AccountsDB stores account data in memory-mapped AppendVec files, indexed by pubkey and slot. It supports fast lookups, handles account deduplication across slots, and periodically cleans up dead accounts. AccountsDB is the largest consumer of validator disk space. Aliases: AccountsDb Relacionados: Bank, Snapshot, AppendVec
Usa contexto del glosario, relaciones entre términos, modelos mentales y builder paths para recibir respuestas estructuradas en vez de output genérico.
Opcional: pega código Anchor, Solana o Rust para que el Copilot mapee primitivas de vuelta al glosario.
El Copilot responderá usando el término actual, conceptos relacionados, modelos mentales y el grafo alrededor del glosario.
Estas ramas muestran qué conceptos toca este término directamente y qué existe una capa más allá de ellos.
An in-memory representation of the accounts state at a specific slot. Each slot gets its own Bank that inherits from its parent slot's Bank. The Bank processes transactions, updates account balances, and tracks execution results. Once a slot is complete, the Bank is frozen and can be snapshotted or used as a parent for the next Bank.
A serialized copy of the full accounts state at a rooted slot, used for fast validator bootstrapping. Full snapshots contain all accounts; incremental snapshots contain only accounts modified since the last full snapshot. New validators download a snapshot instead of replaying the entire ledger history, reducing sync time from days to minutes.
A memory-mapped, append-only file used by AccountsDB to store account data. Each AppendVec corresponds to a specific slot and contains serialized account entries (pubkey, lamports, data, owner, etc.). AppendVecs are immutable once the slot is rooted, enabling efficient snapshotting and cleanup.
Estos son los siguientes conceptos que vale la pena abrir si quieres que este término tenga más sentido dentro de un workflow real de Solana.
Estas entradas son fáciles de mezclar cuando lees rápido, haces prompting a un LLM o estás entrando en una nueva capa de Solana.
The Rust-based Solana validator client maintained by Anza (formerly Solana Labs). Agave is the original and most widely deployed validator implementation. It handles all aspects of validation: TPU, TVU, gossip, AccountsDB, and RPC. The name 'Agave' was adopted to distinguish it from the Firedancer client.
A next-generation consensus protocol proposed in SIMD-0326 that aims to collapse Solana's legacy systems (Proof of History, Tower BFT, gossip-based vote propagation) into two streamlined mechanisms: Rotor for data propagation and Votor for off-chain voting. Alpenglow targets reducing transaction finality from ~12.8 seconds to under 150 milliseconds, representing the most significant consensus overhaul in Solana's history.
A development organization that spun out of Solana Labs in early 2024 to independently maintain and develop the Agave validator client and core Solana toolchain. Anza also maintains the @solana/kit SDK (formerly web3.js v2), the Anchor framework, and the SVM API. The spin-off was intended to decentralize Solana's core development and improve client diversity.
Las entradas del glosario se vuelven útiles cuando están conectadas. Estos enlaces son el camino más corto hacia ideas adyacentes.
An in-memory representation of the accounts state at a specific slot. Each slot gets its own Bank that inherits from its parent slot's Bank. The Bank processes transactions, updates account balances, and tracks execution results. Once a slot is complete, the Bank is frozen and can be snapshotted or used as a parent for the next Bank.
A serialized copy of the full accounts state at a rooted slot, used for fast validator bootstrapping. Full snapshots contain all accounts; incremental snapshots contain only accounts modified since the last full snapshot. New validators download a snapshot instead of replaying the entire ledger history, reducing sync time from days to minutes.
A memory-mapped, append-only file used by AccountsDB to store account data. Each AppendVec corresponds to a specific slot and contains serialized account entries (pubkey, lamports, data, owner, etc.). AppendVecs are immutable once the slot is rooted, enabling efficient snapshotting and cleanup.
Estas entradas viven junto al término actual y ayudan a que la página se sienta parte de un grafo de conocimiento más amplio en lugar de un callejón sin salida.
A clock mechanism that cryptographically proves the passage of time between events. PoH uses a sequential SHA-256 hash chain where each output becomes the next input, creating a verifiable ordering of events without requiring consensus. The leader produces ~400,000 hashes per slot (~400ms), and any validator can verify the sequence in parallel, enabling Solana's high throughput by removing the need for validators to agree on time.
Solana's custom BFT consensus algorithm built on top of Proof of History. Tower BFT uses PoH as a clock to reduce communication overhead in traditional PBFT from O(n²) to O(n). Validators vote on forks with exponentially increasing lockout periods—each consecutive vote doubles the lockout, making rollbacks progressively more expensive. A fork is finalized when it reaches supermajority (66.7%+ of stake).
A time window during which a designated leader validator can produce a block. Each slot lasts approximately 400 milliseconds. Slots are numbered sequentially from genesis and grouped into epochs of 432,000 slots (~2-3 days). Not every slot produces a block—a skipped slot means the leader was offline or too slow.
A set of entries produced by a leader during a single slot. A block contains transactions bundled into entries, each with a PoH hash proving ordering. Blocks are broken into shreds for network propagation via Turbine. Maximum block size is limited by compute units (48M CU cap per block) rather than byte size.