DOCSEARCHbyAlgolia
Submit Docs

Agave Documentation

website·Indexed 35 days ago

https://docs.anza.xyz/

Documentation for running and managing Agave validator nodes on the Solana network. Includes guides on validator setup, RPC node configuration, Solana CLI tool installation, cluster management, and technical deep dives into the validator anatomy, runtime, and Geyser plugin mechanism.

Tokens
72.4K
Snippets
227
Records
530
Agent score
72%

What's inside Agave

  1. Overview of Solana's crypto-economic incentive design

    Solana employs a crypto-economic system to incentivize validation clients to maintain network security and decentralization. The system relies on two primary remittance channels:

    1. Protocol-based (Inflationary) Rewards: These are issued based on a global, protocol-defined inflation rate and a pre-determined disinflationary schedule. Rewards are distributed across actively staked tokens on the network per epoch, providing monetary supply predictability.
    2. Transaction Fees: Market-based transfers paid by users for the inclusion and execution of transactions. A portion of these fees is partially burned to provide long-term economic stability and protection against forking.

    Additionally, the network implements Storage Rent Economics to manage the externality costs associated with maintaining the active state of the ledger.

  2. Overview of Solana's Proof of Stake (PoS) mechanism

    Solana uses a Proof of Stake architecture where token holders stake their tokens to a validator.

    • Stake and Trust: Staked tokens represent trust in a validator. Users retain ownership and can remove their stake at any time.
    • Rewards: Stakers receive a return of tokens as a reward for securing the network.
    • Consensus Power: A validator's vote share in consensus is proportional to the amount of tokens staked to it. This determines the frequency with which a validator is selected as the 'leader' to produce blocks.

  3. Overview of Solana Tower BFT Algorithm

    Tower BFT is Solana's consensus algorithm designed to solve several key problems: recovering from forks not accepted by the supermajority, converging on a single fork among many, managing validator risk for reward-based votes, providing computable costs for rollbacks (Consistency), and resisting attacks from high-speed Proof of History (PoH) ASICs.

  4. Overview of Persistent Account Storage

    Persistent Account Storage is designed to maintain the computed state of all transactions processed by a validator. To balance the cost-effectiveness of persistent storage (NVMe) with the need for high performance, the system uses a data structure that allows for concurrent reads and writes. It utilizes an AppendVec for optimized writes and an account index to track account locations across different forks, eliminating the need for explicit state checkpointing.

  5. Overview of the Geyser Plugin Mechanism

    The Geyser plugin mechanism allows Agave validators to transmit information about accounts, slots, blocks, and transactions to external data stores (e.g., relational databases, NoSQL, or Kafka). This prevents validators from falling behind the network when under heavy RPC loads (such as getProgramAccounts calls) by offloading data consumption to external services that can implement their own caching and indexing optimizations.

  6. Overview of the Cluster Test Framework (CTF)

    The Cluster Test Framework (CTF) is a test harness that allows developers to write tests independent of the cluster deployment method (local in-process or deployed in a data center). It is primarily used to capture regressions and verify cluster stability, consensus, fault tolerance, and API stability. Tests are designed to verify single bugs or scenarios while minimizing internal plumbing exposure.

  7. Overview of Alpenglow Consensus Protocol

    Alpenglow is Solana's consensus protocol that replaces Tower BFT's voting and finality logic with Votor. It is expected to activate as part of the Agave v4.3 release cycle. The protocol targets finality in approximately 150 ms under normal network conditions.

  8. Overview of Solana Command-Line Interface (CLI) tools

    The Solana CLI provides the most direct, flexible, and secure access to Solana accounts and is the primary interface where the Anza core team deploys new functionality. Developers use the CLI to perform core blockchain operations such as creating wallets, sending and receiving SOL tokens, and participating in the cluster by delegating stake.

  9. Overview of Proof of Replication (PoRep)

    Proof of Replication (PoRep) is a protocol designed to prevent network centralization by allowing mining nodes (Archivers) to provide storage capacity for pieces of the ledger. It ensures that data is actually stored by requiring nodes to encrypt a dataset with a public symmetric key using CBC encryption and periodically regenerate hashes based on a signed Proof of History (PoH) value. To optimize verification, the protocol randomly samples encrypted segments and records hashes into the PoH ledger, allowing validators to verify multiple proofs concurrently in a single batch.

  10. Overview of the ZK ElGamal Proof program

    The ZK ElGamal Proof program is a native Solana program used to verify zero-knowledge proofs tailored for Pedersen commitments and twisted ElGamal encryption over the curve25519 elliptic curve. These primitives allow for secure public-key encryption and binding commitments that hide the underlying message until revealed.

    • Program ID: Found in solana_sdk_ids::zk_elgamal_proof_program::ID
    • Instruction Definitions: Available in the ProofInstruction source.

  11. Overview of MVP Economic Features for Anza Solana

    The MVP (Minimum Viable Product) economic features provide the foundational functionality for early pre-testnet and testnet participants. These features are designed to support initial network stability and validator operations before the full long-term sustainable economy is implemented. Key MVP features include:

    • A faucet for delivering testnet SOL to validators for staking and app development.
    • An inflation-based reward mechanism for validators.
    • The ability for users to delegate tokens to validator nodes.
    • The ability for validators to set commission fees on interest earned from delegated tokens.

  12. Overview of the Solana Command Line Interface (CLI)

    The Solana CLI provides the most direct, flexible, and secure access to Solana accounts and is the primary interface where the Anza core team deploys new functionality. It is used for essential tasks such as creating wallets, sending and receiving SOL tokens, and participating in the cluster by delegating stake.