An addition to the ICON distributed ledger that may be validated. Consists of transactions
Blocks are an efficient way to maintain a synchronized state between multiple machines. Instead of synchronizing every transaction individually, multiple transactions are synchronized in a single commit. This scheme of synchronization gives validators more time to form a consensus. This reduces the potential bottleneck that would be caused by network latency if each transaction were sent to all validator machines in individual messages.
The ICON blockchain is based off of a merkle tree (wikipedia). It is also a forward-only-moving global state machine. Each block represents one step forward of the machine. This means updates to the decentralized database containing financial or non-financial information. To fulfill two of the major promises of the blockchain, the global state must be entirely trusted and reproducible at each step.
As such, each block contains information in two categories: metadata about the blockchain itself and information about the updates in this step forward of the global state of the blockchain. The metadata is the version of the blockchain being run. The state-update-data is as follows: current time, block ID, block producer / validator information, transactions in this step, and log information.
The data storage layer is typically one of the most generic, low-level layers in any application. This layer is a building block for less abstract parts of an application to place their data into without worry of formatting or the specifics of data retrieval. The ICON blockchain uses RocksDB, which is a common choice among blockchain clients. The main data structure that we use to store blockchain data is called a trie, which is short for retrieval. Tries make it simple to both insert new data and to check whether important pieces of data like blocks, transactions, or accounts exist in our database.
Block creation is the responsibility of the validators. Validators take turns creating the next block on the blockchain. On their turn, they submit the block they've created to their peer validators so that they can form a consensus on whether the block is valid or not