Terminology
Last updated
Last updated
The following terms are used throughout the Nexis documentation and development ecosystem.
A record in the Nexis ledger that either holds data or is an executable program.
Like an account at a traditional bank, a Nexis account may hold funds called . Like a file in Linux, it is addressable by a key, often referred to as a or pubkey.
The key may be one of:
an ed25519 public key
a program-derived account address (32byte value forced off the ed25519 curve)
a hash of an ed25519 public key with a 32 character string
The address of the program that owns the account. Only the owning program is capable of modifying the account.
A front-end application that interacts with a Nexis cluster.
The result of interpreting all programs on the ledger at a given . It includes at least the set of all holding nonzero .
The smallest unit of measure for consumption of computational resources of the blockchain.
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 fee account in the transaction is the account that 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 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 Nexis.
Info
An account whose signing authority is a program and thus is not controlled by a private key like other accounts.
The prioritization fee is calculated by multiplying the requested maximum compute units by the compute-unit price (specified in increments of 0.000001 lamports per compute unit) rounded up to the nearest lamport.
Transactions should request the minimum amount of compute units required for execution to minimize fees.
A digitally transferable asset.
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.
A contiguous set of on the ledger covered by a . A produces at most one block per .
A unique value () that identifies a record (block). Nexis computes a blockhash from the last of the block.
The number of beneath the current block. The first block after the has height one.
The that produces the genesis (first) of a block chain.
The Nexis program that owns and loads , allowing the program to interface with the runtime.
A computer program that accesses the Nexis server network .
A measure of the network confirmation for the .
A set of maintaining a single .
The maximum number of consumed per transaction.
The wallclock duration between a creating a and creating a .
A that has received a of .
A gossip network connecting all of a .
Some number of after has been deactivated while it progressively becomes available for withdrawal. During this period, the stake is considered to be "deactivating". More info about:
See .
A call from one to another. For more information, see .
A multicast network used to efficiently validate and gain consensus.
An entry on the either a or a .
A preimage resistant over the final contents of an entry, which acts as the globally unique identifier. The hash serves as evidence of:
The specified are those included in the entry
The entry's position with respect to other entries in
See .
The time, i.e. number of , for which a is valid.
When nodes representing 2/3rd of the have a common .
A derived from common entries but then diverged.
The first in the chain.
The configuration file that prepares the for the .
See .
A call to invoke a specific in a . An instruction also specifies which accounts it wants to read or modify, and additional data that serves as auxiliary input to the . A must include at least one instruction in a , and all instructions must complete for the transaction to be considered successful.
Instruction handlers are functions that process from . An instruction handler may contain one or more .
A and corresponding for accessing an account.
A fractional with the value of 0.000000001 .
Within the compute budget, a quantity of is used in the calculation of .
The role of a when it is appending to the .
A sequence of mapped to . The cluster uses the leader schedule to determine which validator is the at any moment in time.
A list of containing signed by . Conceptually, this can be traced back to the , but an actual 's ledger may have only newer to reduce storage, as older ones are not needed for validation of future blocks by design.
A of the at a given . It comprises a affirmation that a it has received has been verified, as well as a promise not to vote for a conflicting (i.e. ) for a specific amount of time, the period.
A type of that can verify it's pointing to a valid . It performs more ledger verification than a and less than a .
A with the ability to interpret the binary encoding of other on-chain programs.
The duration of time for which a is unable to on another .
The structured contents of a . Generally containing a header, array of account addresses, recent , and an array of .
Learn more about the here.
A measure of decentralization, the Nakamoto Coefficient is the smallest number of independent entities that can act collectively to shut down a blockchain. The term was coined by Balaji S. Srinivasan and Leland Lee in .
The used to track work done by in a cluster.
A computer participating in a .
The number of participating in a .
The executable code on Nexis blockchain that interprets the sent inside of each to read and modify accounts over which it has control. These programs are often referred to as "" on other blockchains.
See .
A weighted in a rewards regime. In the , the number of points owed to a during redemption is the product of the earned and the number of lamports staked.
The private key of a .
See .
The public key of the containing a .
A stack of proofs, each of 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 , a Proof of History can be verified in less time than it took to produce.
An additional fee user can specify in the compute budget to prioritize their .
The public key of a .
Fee paid by and to store data on the blockchain. When accounts do not have enough balance to pay rent, they may be Garbage Collected.
See also below. Learn more about rent here: .
Accounts that maintain more than 2 years with of rent payments in their account are considered "rent exempt" and will not incur the .
A or that has reached maximum on a . 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.
The component of a responsible for execution.
Nexis's parallel run-time for .
A fraction of a ; the smallest unit sent between .
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 . Thus, the first signature in transaction can be treated as
The percentage of out of the total leader slots in the current epoch. This metric can be misleading as it has high variance after the epoch boundary when the sample size is small, as well as for validators with a low number of leader slots, however can also be useful in identifying node misconfigurations at times.
A past that did not produce a , because the leader was offline or the 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 , nor expire the oldest recent_blockhash.
Whether a slot has been skipped can only be determined when it becomes older than the latest (thus not-skipped) slot.
The period of time for which each ingests transactions and produces a .
Collectively, slots create a logical clock. Slots are ordered sequentially and non-overlapping, comprising roughly equal real-world time as per .
See .
The of a Nexis .
A on Nexis such as spl-token that facilitates tasks such as creating and using tokens.
Tokens forfeit to the if malicious behavior can be proven.
2/3 of a .
A system . provide cluster state information such as current tick height, rewards values, etc. Programs can access Sysvars via a Sysvar account (pubkey) or by querying via a syscall.
A type of that trusts it is communicating with a valid .
A ledger that estimates wallclock duration.
The Nth in the .
The has the program ID TokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb and includes all the same features as the , but comes with extensions such as confidential transfers, custom transfer logic, extended metadata, and much more.
The has the program ID TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA, and provides the basic capabilities of transferring, freezing, and minting tokens.
per second.
.
One or more signed by a using one or more and executed atomically with only two possible outcomes: success or failure.
The first in a , which can be used to uniquely identify the transaction across the complete .
The number of since the transaction was accepted onto the . A transaction is finalized when its block becomes a .
A set of that may be executed in parallel.
.
A full participant in a Nexis network that produces new . A validator validates the transactions added to the
See .
See .
A reward tally for . A vote credit is awarded to a validator in its vote account when the validator reaches a .
A collection of that allows users to manage their funds.
Some number of after has been delegated while it progressively becomes effective. During this period, the stake is considered to be "activating". More info about: