The first block (slot 0) of a Solana cluster that defines initial configuration: the mint account, initial token supply, built-in program deployments, and cluster parameters. The genesis config is generated by the `solana-genesis` tool and shared among all validators to bootstrap a new cluster.
Empieza por la explicación más corta y útil antes de profundizar.
The first block (slot 0) of a Solana cluster that defines initial configuration: the mint account, initial token supply, built-in program deployments, and cluster parameters. The genesis config is generated by the `solana-genesis` tool and shared among all validators to bootstrap a new cluster.
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.
Bloque Génesis (genesis-block) Categoría: Protocolo Base Definición: The first block (slot 0) of a Solana cluster that defines initial configuration: the mint account, initial token supply, built-in program deployments, and cluster parameters. The genesis config is generated by the `solana-genesis` tool and shared among all validators to bootstrap a new cluster. Relacionados: Libro Mayor (Ledger), Clúster
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.
The complete ordered history of all transactions processed by the Solana cluster. The ledger is composed of sequential blocks (one per slot), each containing entries of transactions ordered by PoH. Validators store the ledger locally in Blockstore, and warehouse nodes or Bigtable archives provide long-term historical access.
A set of validators working together to maintain a single Solana ledger. Solana operates three main clusters: mainnet-beta (production), devnet (development), and testnet (stress testing). Each cluster has its own genesis block, token supply, and independent validator set. Validators in a cluster discover each other via the gossip protocol.
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.
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.
The number of blocks produced in the ledger since the genesis block. Block height increments only for slots that successfully produce a block (skipped slots do not increment it), so block height is always less than or equal to the current slot number. Block height is accessible via the getBlockHeight RPC method and the Clock sysvar.
The process of distributing a newly produced block from the leader to all validators in the cluster. Solana uses Turbine for fast propagation—the leader shreds the block, erasure-codes the shreds, and feeds them into the Turbine tree. Target propagation latency is under 200ms for the full cluster.
Las entradas del glosario se vuelven útiles cuando están conectadas. Estos enlaces son el camino más corto hacia ideas adyacentes.
The complete ordered history of all transactions processed by the Solana cluster. The ledger is composed of sequential blocks (one per slot), each containing entries of transactions ordered by PoH. Validators store the ledger locally in Blockstore, and warehouse nodes or Bigtable archives provide long-term historical access.
A set of validators working together to maintain a single Solana ledger. Solana operates three main clusters: mainnet-beta (production), devnet (development), and testnet (stress testing). Each cluster has its own genesis block, token supply, and independent validator set. Validators in a cluster discover each other via the gossip protocol.
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.