Red

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

Lectura rápida

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

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

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 un bloque de construcción que conecta una definición aislada con el sistema mayor donde vive.

Contexto técnico

Ubica el término dentro de la capa de Solana en la que vive para razonar mejor sobre él.

Clusters, nodos, actores de MEV, routing y entornos operativos.

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.

Epoch Schedule (epoch-schedule)
Categoría: Red
Definición: 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, Configuración Génesis
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

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

Rama

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.

Rama

Configuración 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.

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

É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

Configuración 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.

Red

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.

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

Configuración 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.

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.

Red

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.

Red

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.

Red

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.

Red

TPS (Transacciones 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.