Protocolo Base

Cluster

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.

IDcluster

Leitura rápida

Comece pela explicação mais curta e útil antes de aprofundar.

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.

Modelo mental

Use primeiro a analogia curta para raciocinar melhor sobre o termo quando ele aparecer em código, docs ou prompts.

Pense nisso como parte da engrenagem que mantém a ordenação, execução ou consenso da rede funcionando.

Contexto técnico

Coloque o termo dentro da camada de Solana em que ele vive para raciocinar melhor sobre ele.

Consenso, rotação de líderes, slots, epochs e o runtime.

Por que builders ligam para isso

Transforme o termo de vocabulário em algo operacional para produto e engenharia.

Este termo destrava conceitos adjacentes rapidamente, então funciona melhor quando você o trata como um ponto de conexão, não como definição isolada.

Handoff para IA

Handoff para IA

Use este bloco compacto quando quiser dar contexto aterrado para um agente ou assistente sem despejar a página inteira.

Cluster (cluster)
Categoria: Protocolo Base
Definição: 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.
Relacionados: Validador, Protocolo Gossip, Bloco Gênesis
Glossary Copilot

Faça perguntas de Solana com contexto aterrado sem sair do glossário.

Use contexto do glossário, relações entre termos, modelos mentais e builder paths para receber respostas estruturadas em vez de output genérico.

Explicar este código

Opcional: cole código Anchor, Solana ou Rust para o Copilot mapear primitivas de volta para termos do glossário.

Faça uma pergunta aterrada no glossário

Faça uma pergunta aterrada no glossário

O Copilot vai responder usando o termo atual, conceitos relacionados, modelos mentais e o grafo ao redor do glossário.

Grafo conceitual

Veja o termo como parte de uma rede, não como uma definição sem saída.

Esses ramos mostram quais conceitos esse termo toca diretamente e o que existe uma camada além deles.

Ramo

Validador

A node that participates in the Solana network by validating transactions, voting on blocks, and (when selected as leader) producing new blocks. Validators run the Agave, Firedancer, or Jito client software, require significant hardware (128+ GB RAM, high-core CPU, NVMe SSD), and earn rewards from inflation and transaction fees.

Ramo

Protocolo Gossip

A protocol used by validators to exchange metadata and discover peers without relying on a central server. Gossip propagates contact info, vote status, shred versions, epoch slots, and other protocol messages via CRDS. It does not carry transaction or block data—those use TPU and Turbine respectively.

Ramo

Bloco Gênesis

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.

Próximos conceitos para explorar

Continue a cadeia de aprendizado em vez de parar em uma única definição.

Estes são os próximos conceitos que valem abrir se você quiser que este termo faça mais sentido dentro de um workflow real de Solana.

Protocolo Base

Validador

A node that participates in the Solana network by validating transactions, voting on blocks, and (when selected as leader) producing new blocks. Validators run the Agave, Firedancer, or Jito client software, require significant hardware (128+ GB RAM, high-core CPU, NVMe SSD), and earn rewards from inflation and transaction fees.

Protocolo Base

Protocolo Gossip

A protocol used by validators to exchange metadata and discover peers without relying on a central server. Gossip propagates contact info, vote status, shred versions, epoch slots, and other protocol messages via CRDS. It does not carry transaction or block data—those use TPU and Turbine respectively.

Protocolo Base

Bloco Gênesis

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.

Protocolo Base

Configuração Gênesis

The configuration file that defines the initial state of a Solana cluster at genesis, including the initial token supply, built-in program deployments, cluster parameters (ticks per slot, slots per epoch), fee schedule, and rent configuration. The genesis config is generated by the solana-genesis tool and must be shared identically among all validators to bootstrap a cluster.

Comumente confundido com

Termos próximos em vocabulário, sigla ou vizinhança conceitual.

Essas entradas são fáceis de misturar quando você lê rápido, faz prompting em um LLM ou está entrando em uma nova camada de Solana.

Protocolo Baseconfirmation

Confirmation

A vote by a validator on a block, weighted by the validator's stake. The more stake-weighted confirmations a slot receives, the higher the confidence it will be finalized. RPC methods accept commitment levels (processed, confirmed, finalized) to specify the required confirmation threshold.

Termos relacionados

Siga os conceitos que realmente dão contexto a este termo.

Entradas de glossário só ficam úteis quando estão conectadas. Esses links são o caminho mais curto para ideias adjacentes.

Protocolo Basevalidator

Validador

A node that participates in the Solana network by validating transactions, voting on blocks, and (when selected as leader) producing new blocks. Validators run the Agave, Firedancer, or Jito client software, require significant hardware (128+ GB RAM, high-core CPU, NVMe SSD), and earn rewards from inflation and transaction fees.

Protocolo Basegossip

Protocolo Gossip

A protocol used by validators to exchange metadata and discover peers without relying on a central server. Gossip propagates contact info, vote status, shred versions, epoch slots, and other protocol messages via CRDS. It does not carry transaction or block data—those use TPU and Turbine respectively.

Protocolo Basegenesis-block

Bloco Gênesis

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.

Mais na categoria

Permaneça na mesma camada e continue construindo contexto.

Essas entradas vivem ao lado do termo atual e ajudam a página a parecer parte de um grafo maior, não um beco sem saída.

Protocolo Base

Prova de História (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

Bloco

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.