Protocolo Base

Confirmed Block

A block that has received votes from validators representing a supermajority (66.7%+) of the cluster's active stake, achieving optimistic confirmation. Confirmed blocks are highly likely to be finalized but are not yet irreversible — full finality requires the block to become rooted through 31+ consecutive confirmations in Tower BFT.

IDconfirmed-block

Lectura rápida

Empieza por la explicación más corta y útil antes de profundizar.

A block that has received votes from validators representing a supermajority (66.7%+) of the cluster's active stake, achieving optimistic confirmation. Confirmed blocks are highly likely to be finalized but are not yet irreversible — full finality requires the block to become rooted through 31+ consecutive confirmations in Tower BFT.

Modelo mental

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.

Contexto técnico

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.

Por qué le importa a un builder

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.

Handoff para IA

Handoff para IA

Usa este bloque compacto cuando quieras dar contexto sólido a un agente o asistente sin volcar toda la página.

Confirmed Block (confirmed-block)
Categoría: Protocolo Base
Definición: A block that has received votes from validators representing a supermajority (66.7%+) of the cluster's active stake, achieving optimistic confirmation. Confirmed blocks are highly likely to be finalized but are not yet irreversible — full finality requires the block to become rooted through 31+ consecutive confirmations in Tower BFT.
Relacionados: Bloque, Confirmación Optimista, Supermayoría, Rooted
Glossary Copilot

Haz preguntas de Solana con contexto aterrizado sin salir del glosario.

Usa contexto del glosario, relaciones entre términos, modelos mentales y builder paths para recibir respuestas estructuradas en vez de output genérico.

Abrir workspace completa del Copilot
Explicar este código

Opcional: pega código Anchor, Solana o Rust para que el Copilot mapee primitivas de vuelta al glosario.

Haz una pregunta aterrizada en el glosario

Haz una pregunta aterrizada en el glosario

El Copilot responderá usando el término actual, conceptos relacionados, modelos mentales y el grafo alrededor del glosario.

Grafo conceptual

Ve el término como parte de una red, no como una definición aislada.

Estas ramas muestran qué conceptos toca este término directamente y qué existe una capa más allá de ellos.

Rama

Bloque

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.

Rama

Confirmación Optimista

A transaction confirmation level achieved when 66.7%+ of total stake has voted on the slot, typically within ~400ms. Optimistic confirmation provides high probability of finality without waiting for full root depth. It corresponds to the 'confirmed' commitment level in RPC queries.

Rama

Supermayoría

A threshold of more than 2/3 (66.7%) of total active stake agreeing on a particular fork. Supermajority is required for optimistic confirmation and, through sustained voting, for finality (rooting). If supermajority is lost (e.g., too many validators offline), the cluster halts until it recovers.

Rama

Rooted

A slot that has been finalized by achieving maximum lockout in Tower BFT—meaning 31+ consecutive confirmations have been built on top of it. Once rooted, a slot and its transactions are considered irreversible. Rooted corresponds to the 'finalized' commitment level and takes approximately 12-13 seconds.

Siguientes conceptos para explorar

Mantén la cadena de aprendizaje en movimiento en lugar de parar en una sola definición.

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.

Protocolo Base

Bloque

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.

Protocolo Base

Confirmación Optimista

A transaction confirmation level achieved when 66.7%+ of total stake has voted on the slot, typically within ~400ms. Optimistic confirmation provides high probability of finality without waiting for full root depth. It corresponds to the 'confirmed' commitment level in RPC queries.

Protocolo Base

Supermayoría

A threshold of more than 2/3 (66.7%) of total active stake agreeing on a particular fork. Supermajority is required for optimistic confirmation and, through sustained voting, for finality (rooting). If supermajority is lost (e.g., too many validators offline), the cluster halts until it recovers.

Protocolo Base

Rooted

A slot that has been finalized by achieving maximum lockout in Tower BFT—meaning 31+ consecutive confirmations have been built on top of it. Once rooted, a slot and its transactions are considered irreversible. Rooted corresponds to the 'finalized' commitment level and takes approximately 12-13 seconds.

Comúnmente confundido con

Términos cercanos en vocabulario, acrónimo o vecindad conceptual.

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.

Protocolo Baseblock-propagation

Block Propagation

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.

Protocolo Baseblock

Bloque

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.

Protocolo Basesimd-123

SIMD-123 (Block Revenue Sharing)

A protocol change enabling validators to automatically share block revenue (priority fees and MEV tips) with their delegators through an on-chain mechanism. Validators set a commission rate for block revenue, and the protocol distributes the remainder to delegators at epoch boundaries based on their stake proportion. Available in Agave 3.0+.

AliasBlock Revenue Sharing
Términos relacionados

Sigue los conceptos que realmente le dan contexto a este término.

Las entradas del glosario se vuelven útiles cuando están conectadas. Estos enlaces son el camino más corto hacia ideas adyacentes.

Protocolo Baseblock

Bloque

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.

Protocolo Baseoptimistic-confirmation

Confirmación Optimista

A transaction confirmation level achieved when 66.7%+ of total stake has voted on the slot, typically within ~400ms. Optimistic confirmation provides high probability of finality without waiting for full root depth. It corresponds to the 'confirmed' commitment level in RPC queries.

Protocolo Basesupermajority

Supermayoría

A threshold of more than 2/3 (66.7%) of total active stake agreeing on a particular fork. Supermajority is required for optimistic confirmation and, through sustained voting, for finality (rooting). If supermajority is lost (e.g., too many validators offline), the cluster halts until it recovers.

Protocolo Baserooted

Rooted

A slot that has been finalized by achieving maximum lockout in Tower BFT—meaning 31+ consecutive confirmations have been built on top of it. Once rooted, a slot and its transactions are considered irreversible. Rooted corresponds to the 'finalized' commitment level and takes approximately 12-13 seconds.

Más en la categoría

Quédate en la misma capa y sigue construyendo contexto.

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.

Protocolo Base

Prueba de Historia (PoH)

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.

Protocolo Base

Tower BFT

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).

Protocolo Base

Slot

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.

Protocolo Base

Bloque

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.