The following terms are used throughout the documentation.
A front-end application that interacts with a Solana cluster.
Smallest encrypted chunk of ledger, an encrypted ledger segment would be made of many CBC blocks.
ledger_segment_size / cbc_block_size to be exact.
Some number of epochs after stake has been deactivated while it progressively becomes available for withdrawal. During this period, the stake is considered to be "deactivating". More info about: warmup and cooldown
See vote credit.
A multicast network used to efficiently validate entries and gain consensus.
An off-chain service that acts as a custodian for a user's private key. It typically serves to validate and sign transactions.
- The entry being generated after a duration of time
- The specified transactions are those included in the entry
- The entry's position with respect to other entries in ledger
See Proof of History.
The fee account in the transaction is the account pays for the cost of including the transaction in the ledger. This is the first account in the transaction. This account must be declared as Read-Write (writable) in the transaction since paying for the transaction reduces the account balance.
A ledger derived from common entries but then diverged.
The first block in the chain.
A digital fingerprint of a sequence of bytes.
An increase in token supply over time used to fund rewards for validation and to fund continued development of Solana.
A list of entries containing transactions signed by clients. Conceptually, this can be traced back to the genesis block, but actual validators's ledger may have only newer blocks to save storage usage as older ones not needed for validation of future blocks by design.
A hash of the validator's state at a given tick height. It comprises a validator's affirmation that a block it has received has been verified, as well as a promise not to vote for a conflicting block (i.e. fork) for a specific amount of time, the lockout period.
A program with the ability to interpret the binary encoding of other on-chain programs.
A computer participating in a cluster.
See Proof of History.
A weighted credit in a rewards regime. In the validator rewards regime, the number of points owed to a stake during redemption is the product of the vote credits earned and the number of lamports staked.
The private key of a keypair.
The code that interprets instructions.
A stack of proofs, each which proves that some data existed before the proof was created and that a precise duration of time passed before the previous proof. Like a VDF, a Proof of History can be verified in less time than it took to produce.
The public key of a keypair.
A block or slot that has reached maximum lockout on a validator. The root is the highest block that is an ancestor of all active forks on a validator. All ancestor blocks of a root are also transitively a root. Blocks that are not an ancestor and not a descendant of the root are excluded from consideration for consensus and can be discarded.
A 64-byte ed25519 signature of R (32-bytes) and S (32-bytes). With the requirement that R is a packed Edwards point not of small order and S is a scalar in the range of 0 <= S < L. This requirement ensures no signature malleability. Each transaction must have at least one signature for fee account. Thus, the first signature in transaction can be treated as transacton id
A past slot that did not produce a block, because the leader was offline or the fork containing the slot was abandoned for a better alternative by cluster consensus. A skipped slot will not appear as an ancestor for blocks at subsequent slots, nor increment the block height, nor expire the oldest
Whether a slot has been skipped can only be determined when it becomes older than the latest rooted (thus not-skipped) slot.
Collectively, slots create a logical clock. Slots are ordered sequentially and non-overlapping, comprising roughly equal real-world time as per PoH.
A set of constraints that once satisfied, signal to a program that some predefined account updates are permitted.
2/3 of a cluster.
A synthetic account maintained by the runtime and provided to programs which provide cluster state such as current tick height, rewards points values, etc. Sysvars can either be passed to the program as an account or queried by the program via a syscall.
A ledger entry that estimates wallclock duration.
A scarce, fungible member of a set of tokens.
Transactions per second.
A set of transactions that may be executed in parallel.
A function that takes a fixed amount of time to execute that produces a proof that it ran, which can then be verified in less time than it took to produce.
See ledger vote.
A collection of keypairs.