A sysvar (address: SysvarC1ock11111111111111111111111111111111) that provides the current slot, epoch, unix_timestamp, and leader_schedule_epoch. Programs use Clock to implement time-based logic like lockups or vesting schedules. In Anchor, accessed via `Clock::get()` or as a sysvar account in the accounts struct.
Empieza por la explicación más corta y útil antes de profundizar.
A sysvar (address: SysvarC1ock11111111111111111111111111111111) that provides the current slot, epoch, unix_timestamp, and leader_schedule_epoch. Programs use Clock to implement time-based logic like lockups or vesting schedules. In Anchor, accessed via `Clock::get()` or as a sysvar account in the accounts struct.
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 una de las piezas centrales que tu programa lee, escribe o invoca durante la ejecución.
Ubica el término dentro de la capa de Solana en la que vive para razonar mejor sobre él.
Accounts, instrucciones, PDAs, transacciones y flujo de ejecución.
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.
Clock Sysvar (clock) Categoría: Modelo de Programación Definición: A sysvar (address: SysvarC1ock11111111111111111111111111111111) that provides the current slot, epoch, unix_timestamp, and leader_schedule_epoch. Programs use Clock to implement time-based logic like lockups or vesting schedules. In Anchor, accessed via `Clock::get()` or as a sysvar account in the accounts struct. Relacionados: Sysvar, Slot, Época
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.
Special read-only accounts maintained by the runtime that expose cluster state to programs. Key sysvars include Clock (slot, timestamp), Rent (lamports-per-byte), EpochSchedule (epoch parameters), RecentBlockhashes, StakeHistory, and Fees. Programs access sysvars by including the sysvar account in the instruction or via the sol_get_sysvar syscall.
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 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.
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.
Special read-only accounts maintained by the runtime that expose cluster state to programs. Key sysvars include Clock (slot, timestamp), Rent (lamports-per-byte), EpochSchedule (epoch parameters), RecentBlockhashes, StakeHistory, and Fees. Programs access sysvars by including the sysvar account in the instruction or via the sol_get_sysvar syscall.
Las entradas del glosario se vuelven útiles cuando están conectadas. Estos enlaces son el camino más corto hacia ideas adyacentes.
Special read-only accounts maintained by the runtime that expose cluster state to programs. Key sysvars include Clock (slot, timestamp), Rent (lamports-per-byte), EpochSchedule (epoch parameters), RecentBlockhashes, StakeHistory, and Fees. Programs access sysvars by including the sysvar account in the instruction or via the sol_get_sysvar syscall.
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 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.
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.
The fundamental data storage unit on Solana. Every piece of state is stored in an account identified by a 32-byte public key. Accounts hold a lamport balance, an owner program, a data byte array (up to 10MB), and an executable flag. Only the owning program can modify an account's data, but anyone can credit lamports to it.
Executable code deployed on-chain, equivalent to a smart contract on other blockchains. Programs are stateless—they store no data themselves but read/write data in separate accounts they own. Programs are compiled to SBF bytecode and loaded via the BPF Loader. Every program has a unique Program ID (its account's public key).
A single operation within a transaction that invokes a program. An instruction specifies: (1) the program ID to call, (2) an array of account metas (pubkey, is_signer, is_writable), and (3) an opaque data byte array. Programs decode the instruction data to determine which operation to perform.
An atomic unit of execution containing one or more instructions, a recent blockhash, and one or more signatures. All instructions in a transaction execute sequentially and atomically—if any instruction fails, the entire transaction reverts. Transactions have a 1,232-byte size limit (matching IPv6 MTU) and a default 200,000 CU budget.