Accumulator Root Hash
- An accumulator root hash is the root hash of a Merkle accumulator.
- An account in the Aptos blockchain is a container for an arbitrary number of Move modules and Move resources. This essentially means that the state of each account is comprised of both code and data.
- The account is identified by an account address.
- The address of a Aptos account, see basics on accounts.
- AptosBFT is the Aptos protocol's BFT consensus algorithm.
- AptosBFT is based on HotStuff.
- The Aptos blockchain is a ledger of immutable transactions agreed upon by the validators on the Aptos network (the network of validators).
Aptos-core is the open source technology on which the Aptos Payment Network runs. Aptos-core contains software for
- the Aptos blockchain itself, which generates and stores the immutable ledger of confirmed transactions and
- the validation process, which implements the consensus algorithm to validate transactions and add them to the Aptos blockchain immutable ledger.
The Aptos Framework defines the public API for blockchain updates and the structure of on-chain data. It defines the business logic and access control for the three key pillars of Aptos functionality: payments, treasury, and on-chain governance. It is implemented as a set of modules written in the Move programming language and stored on-chain as Move bytecode.
An Aptos node is a peer entity of the Aptos network that tracks the state of the Aptos blockchain. There are two types of Aptos nodes, validators and fullnodes).
- Aptos protocol is the specification of how transactions are submitted, ordered, executed, and recorded within the Aptos network.
AptosAccountis a Move resource that holds all the administrative data associated with an account, such as sequence number, balance, and authentication key.
AptosAccountis the only resource that every account is guaranteed to contain.
- The AptosAccount module is a Move module that contains the code for manipulating the administrative data held in a particular
- Code for checking or incrementing sequence numbers, withdrawing or depositing currency, and extracting gas deposits is included in the AptosAccount module.
- See devnet.
- A validator that does not follow the specification of the consensus protocol, and wishes to compromise the correct execution of the protocol.
- BFT algorithms traditionally support up to one-third of the algorithm's voting power being held by Byzantine validators.
Byzantine Fault Tolerance (BFT)
- Byzantine Fault Tolerance (BFT) is the ability of a distributed system to provide safety and liveness guarantees in the presence of faulty, or “Byzantine,” validators below a certain threshold.
- The Aptos blockchain uses AptosBFT, a consensus protocol based on HotStuff.
- BFT algorithms typically operate with a number of entities, collectively holding N votes (which are called “validators” in the Aptos network’s application of the system).
- N is chosen to withstand some number of validators holding f votes, which might be malicious.
- In this configuration, N is typically set to 3f+1. Validators holding up to f votes will be allowed to be faulty — offline, malicious, slow, etc. As long as 2f+1 votes are held by honest validators, they will be able to reach consensus on consistent decisions.
- This implies that BFT consensus protocols can function correctly, even if up to one-third of the voting power is held by validators that are compromised or fail.
- Consensus is a component of a validator.
- The consensus component is responsible for coordination and agreement amongst all validators on the block of transactions to be executed, their order, and the execution results.
- The Aptos blockchain is formed with these agreed-upon transactions and their corresponding execution results.
- A consensus protocol is collectively executed by n validators to accept or reject a transaction and to agree on the ordering of transactions and execution results.
- See BFT
- The devnet is a publicly deployed instance of the Aptos network that runs using a set of validator test nodes.
- The devnet is a demonstration of the Aptos network that is built for experimenting with new ideas
- The devnet simulates a digital payment system and the coins on the devnet have no real world value.
- Ed25519 is our supported digital signature scheme.
- More specifically, the Aptos network uses the PureEdDSA scheme over the Ed25519 curve, as defined in RFC 8032.
- An event is the user-facing representation of the effects of executing a transaction.
- A transaction may be designed to emit any number of events as a list. For example, a
Coin<AptosCoin>transfer emits a
WithdrawEventfor the sender account and a
DepositEventfor the recipient account.
- In the Aptos protocol, events provide evidence that the successful execution of a transaction resulted in a specific effect. The
DepositEvent(in the above example) allows the recipient to confirm that a payment was received into their account.
- Events are persisted on the blockchain and are used to answer queries by clients.
A transaction ceases to be valid after its expiration time. If it is assumed that:
- Time_C is the current time that is agreed upon between validators (Time_C is not the local time of the client);
- Time_E is the expiration time of a transaction T_N; and
- Time_C > Time_E and transaction T_N has not been included in the blockchain,
then there is a guarantee that T_N will never be included in the blockchain.
- Faucet is the way to create Aptos currency with no real-world value, only on our devnet.
- The Faucet is a service running along with the devnet. This service only exists to facilitate minting coins for the devnet.
- You can use the Faucet by sending a request to create coins and transfer them into a given account on your behalf.
- Gas is a way to pay for computation and storage on a blockchain network. All transactions on the Aptos network cost a certain amount of gas.
- The gas required for a transaction depends on the size of the transaction, the computational cost of executing the transaction, and the amount of additional global state created by the transaction (e.g., if new accounts are created).
- The purpose of gas is regulating demand for the limited computational and storage resources of the validators, including preventing denial of service (DoS) attacks.
- Each transaction specifies the gas price the sender is willing to pay. Gas price is specified in currency/gas units.
- The price of gas required for a transaction depends on the current demand for usage of the network.
- The gas cost is fixed at a point in time. Gas costs are denominated in gas units.
- A validator that faithfully executes the consensus protocol and is not Byzantine.
- HotStuff is a recent proposal for a BFT consensus protocol.
- AptosBFT, the Aptos network's consensus algorithm, is based on HotStuff.
- It simplifies the reasoning about safety, and it addresses some performance limitations of previous consensus protocols.
- A leader is a validator that proposes a block of transactions for the consensus protocol.
- In leader-based protocols, nodes must agree on a leader to make progress.
- Leaders are selected by a function that takes the current round number as input.
Maximum Gas Amount
- The Maximum Gas Amount of a transaction is the maximum amount of gas the sender is ready to pay for the transaction.
- The gas charged is equal to the gas price multiplied by units of gas required to process this transaction. If the result is less than the max gas amount, the transaction has been successfully executed.
- If the transaction runs out of gas while it is being executed or the account runs out of balance during execution, then the sender will be charged for gas used and the transaction will fail.
- Mempool is one of the components of the validator. It holds an in-memory buffer of transactions that have been submitted but not yet agreed upon and executed. Mempool receives transactions from JSON-RPC Service.
- Transactions in the mempool of a validator are added from the JSON-RPC Service of the current node and from the mempool of other Aptos nodes.
- When the current validator is the leader, its consensus component pulls the transactions from its mempool and proposes the order of the transactions that form a block. The validator quorum then votes on the proposal.
- Merkle tree is a type of authenticated data structure that allows for efficient verification of data integrity and updates.
- The Aptos network treats the entire blockchain as a single data structure that records the history of transactions and states over time.
- The Merkle tree implementation simplifies the work of apps accessing the blockchain. It allows apps to:
- Read any data from any point in time.
- Verify the integrity of the data using a unified framework.
- The Merkle Accumulator is an append-only Merkle tree that the Aptos blockchain uses to store the ledger.
- Merkle accumulators can provide proofs that a transaction was included in the chain (“proof of inclusion”).
- They are also called "history trees" in literature.
- Move is a new programming language that implements all the transactions on the Aptos blockchain.
- It has two different kinds of code — transaction scripts and Move modules.
- Move programs are compiled into Move bytecode.
- Move bytecode is used to express transaction scripts and Move modules.
- A Move module defines the rules for updating the global state of the Aptos blockchain.
- In the Aptos protocol, a Move module is a smart contract.
- Each user-submitted transaction includes a transaction script. The transaction script invokes procedures of one or more Move modules to update the global state of the blockchain according to the rules.
- Move resources contain data that can be accessed according to the procedures declared in a Move module.
- Move resources can never be copied, reused, or lost. This protects Move programmers from accidentally or intentionally losing track of a resource.
Move Virtual Machine (MVM)
- The Move virtual machine executes transaction scripts written in Move bytecode to produce an execution result. This result is used to update the blockchain state.
- The virtual machine is part of a validator.
- A node is a peer entity of the Aptos network that tracks the state of the Aptos blockchain.
- An Aptos node consists of logical components. Mempool, consensus, and the virtual machine are examples of node components.
- Open-source community is a term used for a group of developers who work on open-source software. If you're reading this glossary, then you are part of the Aptos project's developer community.
- A proof is a way to verify the accuracy of data in the blockchain.
- Every operation in the Aptos blockchain can be verified cryptographically that it is indeed correct and that data has not been omitted.
- For example, if a user queries the information within a particular executed transaction, they will be provided with a cryptographic proof that the data returned to them is correct.
A resource account is used to manage resources independent of an account managed by a user. For example, a developer may use a resource account to manage an account for module publishing, say managing a contract.
The contract itself does not require a signer post initialization. A resource account gives you the means for the module to provide a signer to other modules and sign transactions on behalf of the module.
See Resource accounts.
- The REST Service component is the external interface of a Aptos node. Any incoming client request, such as submitted transactions or queries, must first go through the REST Service. A client needs to go through the REST Service component to access storage or any other component in the system. This filters requests and protects the system.
- Whenever a client submits a new transaction, the REST Service passes it to mempool.
- A round consists of achieving consensus on a block of transactions and their execution results.
- A round number is a shared counter used to select leaders during an epoch of the consensus protocol.
- The sequence number for an account indicates the number of transactions that have been submitted and committed on chain from that account. It is incremented every time a transaction sent from that account is executed or aborted and stored in the blockchain.
- A transaction is executed only if it matches the current sequence number for the sender account. This helps sequence multiple transactions from the same sender and prevents replay attacks.
- If the current sequence number of an account A is X, then a transaction T on account A will only be executed if T's sequence number is X.
- These transactions will be held in mempool until they are the next sequence number for that account (or until they expire).
- When the transaction is applied, the sequence number of the account will become X+1. The account has a strictly increasing sequence number.
- Alternate name: Sender address.
- Sender is the address of the originator account for a transaction. A transaction must be signed by the originator.
- See Move Module.
- A state in the Aptos protocol is a snapshot of the distributed database.
- A transaction modifies the database and produces a new and updated state.
State Root Hash
- State root hash is a Merkle hash over all keys and values the state of the Aptos blockchain at a given version.
- A table implements the Table type and in Aptos is used to store information as key-value data within an account at large scale.
table.move for the associated Aptos source file.
- A raw transaction contains the following fields:
- A signed transaction is a raw transaction with the digital signature.
- An executed transaction changes the state of the Aptos blockchain.
- Each transaction submitted by a user includes a transaction script.
- It represents the operation a client submits to a validator.
- The operation could be a request to move coins from user A to user B, or it could involve interactions with published Move modules/smart contracts.
- The transaction script is an arbitrary program that interacts with resources published in the global storage of the Aptos blockchain by calling the procedures of a module. It encodes the logic for a transaction.
- A single transaction script can send funds to multiple recipients and invoke procedures from several different modules.
- A transaction script is not stored in the global state and cannot be invoked by other transaction scripts. It is a single-use program.
- Alternate name: Validators.
- A validator is an entity of the Aptos ecosystem that validates on the Aptos blockchain. It receives requests from clients and runs consensus, execution, and storage.
- A validator maintains the history of all the transactions on the blockchain.
- Internally, a validator needs to keep the current state, to execute transactions, and to calculate the next state.
- A version is also called “height” in blockchain literature.
- The Aptos blockchain doesn't have an explicit notion of a block — it only uses blocks for batching and executing transactions.
- A transaction at height 0 is the first transaction (genesis transaction), and a transaction at height 100 is the 101st transaction in the transaction store.
An Aptos transaction is well formed if each of the following conditions are true for the transaction:
- The transaction has a valid signature.
- An account exists at the sender address.
- It includes a public key, and the hash of the public key matches the sender account's authentication key.
- The sequence number of the transaction matches the sender account's sequence number.
- The sender account's balance is greater than the maximum gas amount.
- The expiration time of the transaction has not passed.