How Solana Works: An Executive Overview

   

This is the second part of this article. Here is the first part.

Let’s discover more about how Solana works:

Proof of History (PoH)

Proof of History (PoH) stands out as a breakthrough in the Solana blockchain. It acts as a cryptographic timekeeping device that establishes a confirmed sequence of events and time stamps without needing constant validator communication.

Unlike the PoW, PoH complements Solana’s PoS by enabling efficient transaction processing.

Key Features of PoH

• Deterministic Hashing:  The SHA256 algorithm underlies PoH, ensuring that the same input produces the same hash, with outputs always being 256 bits. This feature makes sure people can rebuild the chain of events.
• Sequential Computation:  Validators keep a running string of SHA256 hashes going, with each hash taking the previous one’s output as its input. This sequence builds a checkable “mini proof of work,” backing up the flow of time and the order of transactions.
• Efficient Verification:  Creating these hashes needs step-by-step computing. Other validators can also check if a given set of hashes is right all at once, making the system both safe and productive.
• Trusted Timestamps:  Using trusted timestamps in messages also prevents validators from making blocks and sticking to the leader’s schedule.

During a leader’s slot, the PoH service integrates processed entries from transactions with the current PoH hash, creating a cryptographic record of the transactions. This record not only timestamps the transactions but also establishes their sequence. The leader selected via the proof-of-stake system has a vital part to play in this process. They make sure they add new entries.

Accounts Model

In Solana, they maintain the global state in a specialized database called AccountsDB. This system keeps all accounts in a key-value structure. The account address serves as the key, while the account data acts as the value.

The idea that ‘Everything on Solana is an account!’ shapes its design. This means tokens, smart contracts, and other elements exist as accounts. This setup creates a solid and adaptable framework, allowing different apps to run on the platform.

Types of Accounts

• User Accounts: These are basic accounts that private keys control. People often use them to hold SOL tokens.
• Data Accounts: This stores state information such as token balances or other app-specific data.
• Program Accounts:  It stores executable bytecode that allows users to run smart contracts. Solana segregates the runnable code from the state, which improves performance and security.

  Native Program Accounts

  These are programs already set up on the network. They perform the Vote Program and the BPF Loader.

  A Solana account holds information like the owner’s public key, the amount in lamports, and relevant data.

  Rent and Account Storage

  Solana uses a rent mechanism to manage state bloat. To keep an account running, users need to maintain a particular balance, called the “rent-exempt” amount.

  When an account is no longer in use, you can shut it down and take your rent-exempt SOL back.

• Turbine

  Solana disseminates transaction data across the network using Turbine. It divides the transaction data into small lots known as “shreds”.

  Afterwards, it employs a tree-like structure to distribute these data to all validators.

  Shredding and Data Propagation

  • Shredding: First, transactions are into shreds and then sent to validators within the system. Every tiny piece contains a part of the transaction data, so they encode it with Forward Error Correction (FEC).

  This classification handles the integrity of the data; even if the system loses or corrupts some shreds, this data is still saved.

• • Secure Transactions with Merkle Trees: The leader signs the root of each merkerized batch of shreds. That is the root, and guardians submit shreds associated with the Merkle root to confirm that the data is genuine.
  • Tree Structure: The system structures the validators in a tabular manner under the “Turbine Tree,” which means the data transfer is more efficient and reduces the load on any single node.
  • Consensus: Solana reaches a consensus by combining PoH and Tower BFT (TBFT), a tweaked version of Practical Byzantine Fault Tolerance (PBFT). This approach engages the compulsory sort PoH in the consensus process to make it more lucid.

  • Voting and Forks

    • Voting: Validators can vote on whether blocks are valid, and these votes are the basis for the transactions in the chain. Validators get the highest score among a cluster; the rewards will be the correct and timely processing of the processes.
    • Handling Forks: Solana enables different blocks to exist from a single parent block, which results in forks. Validators vote for such forks, and the chain selects the fork with the highest votes.

  • 
    

  • Finalization and Confirmation

    A transaction will advance from ‘processed’ to ‘confirmed’ to ‘finalized’ as more validators vote on its relevance. This multi-stage process, along with Solana’s security features, assures the audience of security.

    Gossip and Archive

    The gossip network serves as the communication backbone for Solana. It distributes metadata and status updates among validators and other network participants. It uses a modified PlumTree algorithm for efficient information propagation.

    Archive Nodes

    Solana stood out as a project that only needed nodes to digest the whole history to work with it. Instead, “archive” nodes keep an entire record and give access to historical data. This method reduces the storage responsibility of the validators and improves network efficiency.

    Economics and Jito

    Solana’s monetary policy involves using an inflationary peg to incentivize validators. The starting inflation rate was set at 8%, which they brought down to 1.5% annually. Because of Jito’s incentivization, validators can increase their staking rewards. Jito is the alternative client outside SOL’s protocol that conducts the auctions of off-chain block space. Here, the highest bidder receives the desired block.

    Liquid Staking

     enables you to stake your tokens and get benefits while holding liquidity through LSTs. When the user stakes $SOL, they can trade or use the tokens in applications.