The leader is an elected proof of history generator, taking in arbitrary user transactions and converting them into a proof of history sequence of the transactions. This guarantees a unique global order in the system. Following each transaction batch, the leader outputs a signature of the state that is the result of running the transactions in that particular sequence 

Leader and Proof of History

State refers to a naïve hash table indexed by the users address. It contains the users address and the memory required for the computation. 

State

Verifier nodes replicate the blockchain state and provide high availability of the blockchain state. The replication target is selected through the consensus algorithm, ,and the validators in the consensus algorithm select and vote the proof of replication nodes they approve of.

Verifier and State Replication

Validators nodes consume bandwidth from verifiers. Validators are virtual nodes running either on the same machine as the verifiers or the leader, or on different machines altogether.  

Validators

- Leader and Proof of History
- State
- Verifier and State Replication
- Validators

University of Connecticut

- Components
- Network Limits
- Computational Limits
- Memory Limits
- High Performance Smart Contracts 

Solana - System Architecture

Solana - A new architecture for a high performance blockchain

Components

The leader is expected to take in incoming user packets and efficiently order them into a proof of history sequence, which is then published to downstream verifiers. Efficiency is determined based on the memory access patterns of the transactions, so transactions are ordered to minimize faults and maximize prefetching. 

Network Limits

Each transaction needs a digest verification. Because it does not use any memory outside the transaction message itself, the operation can be parallelized independently. Output is therefore limited by the number of cores in the system. 

Computational Limits

A naïve implementation of the state would theoretically fit 10 billion accounts into 640 GB. Based on 2 reads and 2 writes per transaction, memory throughput can handle 2.75 million transactions per second.

Memory Limits

Smart contracts are a generalized form of transactions. They are programs running on each node to modify the state. One of its advantages is a zero cost foreign function interface intrinsic, which are functions implemented on the platform directly and therefore callable by programs. Calling the intrinsic suspends that program and schedules the intrinsic on a higher performance server. 

Learn Before

Related

Learn After