Rede

Epoch Schedule

The configuration that defines the length of an epoch in slots and governs how epoch boundaries are calculated on a Solana cluster. On mainnet-beta, each epoch is 432,000 slots (approximately 2-3 days at 400ms per slot). The epoch schedule determines when staking rewards are distributed, when stake activations and deactivations take effect, and when the leader schedule is recalculated. It is set at genesis and queryable via the getEpochSchedule RPC method.

IDepoch-schedule

Leitura rápida

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

The configuration that defines the length of an epoch in slots and governs how epoch boundaries are calculated on a Solana cluster. On mainnet-beta, each epoch is 432,000 slots (approximately 2-3 days at 400ms per slot). The epoch schedule determines when staking rewards are distributed, when stake activations and deactivations take effect, and when the leader schedule is recalculated. It is set at genesis and queryable via the getEpochSchedule RPC method.

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 um bloco de construção que ajuda a ligar uma definição isolada ao sistema maior onde ela vive.

Contexto técnico

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

Clusters, nós, atores de MEV, roteamento e ambientes operacionais.

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.

Epoch Schedule (epoch-schedule)
Categoria: Rede
Definição: The configuration that defines the length of an epoch in slots and governs how epoch boundaries are calculated on a Solana cluster. On mainnet-beta, each epoch is 432,000 slots (approximately 2-3 days at 400ms per slot). The epoch schedule determines when staking rewards are distributed, when stake activations and deactivations take effect, and when the leader schedule is recalculated. It is set at genesis and queryable via the getEpochSchedule RPC method.
Relacionados: Época, Slot, Configuração 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

Época

A period of 432,000 slots (approximately 2-3 days) that defines a staking cycle. At each epoch boundary, the leader schedule is recalculated based on stake weights, stake activations/deactivations take effect, and inflation rewards are distributed to validators and delegators.

Ramo

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.

Ramo

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.

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

Época

A period of 432,000 slots (approximately 2-3 days) that defines a staking cycle. At each epoch boundary, the leader schedule is recalculated based on stake weights, stake activations/deactivations take effect, and inflation rewards are distributed to validators and delegators.

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

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.

Rede

Fee Market (Local/Global)

Solana operates a local fee market rather than a global one: priority fee competition is scoped to transactions that contend for the same writable accounts, so congestion on one hot account (e.g., a popular AMM pool) does not raise fees for unrelated transactions. This account-centric model means that a highly contested token mint or DEX pool can require very high priority fees to land while other transactions proceed cheaply in parallel. The local fee market is enforced by the scheduler's per-account fee-priority ordering.

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 Baseepoch

Época

A period of 432,000 slots (approximately 2-3 days) that defines a staking cycle. At each epoch boundary, the leader schedule is recalculated based on stake weights, stake activations/deactivations take effect, and inflation rewards are distributed to validators and delegators.

Protocolo Baseslot

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 Basegenesis-config

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.

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.

Rede

Mainnet Beta

Solana's primary production cluster where real SOL and real economic activity occur; the "beta" designation reflects the network's ongoing protocol development despite being fully live since March 2020. It uses the same architecture as other clusters but with real validator stakes, live staking rewards, and permanent on-chain state. All production dApps, tokens, and NFTs exist on Mainnet Beta.

Rede

Devnet

A persistent public Solana cluster intended for application development and testing, running the same software version as Mainnet Beta but with no real economic value. Devnet SOL can be freely airdropped via the CLI or faucet APIs, and the ledger may be reset periodically by Solana Labs. Developers use Devnet to test programs and integrations before deploying to Mainnet Beta.

Rede

Testnet

A public Solana cluster used primarily by the Solana core team and validators to test new software releases, performance benchmarks, and network upgrades under real network conditions before they reach Mainnet Beta. Testnet SOL has no monetary value, and the ledger is reset more frequently than Devnet; it is less suitable for application development and more suited for validator operators validating their infrastructure.

Rede

TPS (Transações por Segundo)

The rate at which a Solana cluster processes and commits transactions; Solana's theoretical maximum exceeds 65,000 TPS due to its parallel execution model, though real-world sustained throughput on Mainnet Beta typically ranges from 2,000–5,000 non-vote TPS under normal load. Vote transactions (used for consensus) make up a significant portion of all on-chain activity and are counted separately. High TPS is enabled by Proof of History timestamps, Sealevel parallel execution, and Gulf Stream mempool-less forwarding.