snarkos-consensus
| Crates.io | snarkos-consensus |
| lib.rs | snarkos-consensus |
| version | 1.3.17 |
| source | src |
| created_at | 2020-08-27 01:12:46.921524 |
| updated_at | 2021-10-25 21:00:02.42883 |
| description | Consensus for a decentralized operating system |
| homepage | https://aleo.org |
| repository | https://github.com/AleoHQ/snarkOS |
| max_upload_size | |
| id | 281193 |
| size | 144,208 |
Howard Wu (howardwu)
documentation
README
snarkos-consensus
snarkOS-consensus defines the consensus mechanisms of the Aleo network - how blocks are validated, block rewards are issued, block times/difficulties are established, and how blocks are mined.
Blocks
Block Difficulty and Block Times
The block time is the amount of time it takes for the network to produce a valid block. This block time is variable and based on the network's hashrate, but regulated by the block difficulty. The block difficulty is adjusted according to the most recent block times in order to regulate and stabilize the average block time of the network.
Block Rewards
A block reward is the total amount of Aleo credits rewarded to the address that mined a block. This value is the base block reward in addition to the fees paid by all transactions included in the block.
| Block Number | Reward |
|---|---|
| 0 - 3,503,999 | 150 ALEO |
| 3,504,000 - 7,007,999 | 75 ALEO |
| 7,008,000 - ∞ | 37.5 ALEO |
Initially, each Aleo block reward is worth 150 Aleo credits. This block reward is halved after every 3,504,000 blocks, which is approximately four years at an estimated 100 blocks per hour. After two iterations of halving the block reward, it will remain at 37.5 for perpetuity.
Verification
Block validation is the process in which the consensus checks that a block is valid in the ledger. A block is valid if all the transactions in the block are valid, the total value balance of the block transactions is correct, there are no double spends, and the block header attributes are valid - timestamp, nonce, PoSW proof, merkle root hash, difficulty target, etc.
Memory Pool
Full nodes need to keep track of transactions that are eligible to be included in future blocks. Because these unconfirmed transactions are not yet included in the ledger, the node stores them in memory, hence the memory pool.
Transactions are removed from the memory pool when the node is shut down or when the transactions are included in valid blocks.
Transactions that are included in stale blocks, can be re-added into the memory pool because they no longer conflict with a transaction on the longest chain.
Miner
The miner is a CPU implementation of an Aleo miner that fetches transactions from the memory pool and attempts to compute a valid nonce for solving a Proof of Succinct Work puzzle.
Upon successfully finding a valid block, miners are compensated with a block reward for their contribution.