Entiende cómo Solana ejecuta trabajo antes de optimizar o debuggear.
La ruta está ordenada para reducir cambio de contexto. Empieza arriba, abre cada término y usa los enlaces relacionados cuando un concepto necesite más profundidad.
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.
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.
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.
The component of the SVM responsible for loading programs, enforcing account access rules (ownership, writability, signer checks), managing compute budgets, and executing transactions. The runtime ensures programs can only modify accounts they own, charges rent, and enforces the 10MB per-transaction account data limit.
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.
La ruta está ordenada para reducir cambio de contexto. Empieza arriba, abre cada término y usa los enlaces relacionados cuando un concepto necesite más profundidad.
Lee la ruta en orden en lugar de saltar aleatoriamente entre términos.
Abre las páginas de término siempre que un concepto necesite definiciones, aliases y enlaces relacionados.
Usa términos relacionados y continuación por categoría para profundizar sin perder el contexto de la ruta.
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.
Empieza por las abstracciones en las que la mayoría de los equipos confía para enviar programas rápido.
Aprende el vocabulario de trading y liquidez detrás de la capa de apps.