jito-solana

The @solana/web3.js library has been moved to its own dedicated repository. For the latest documentation, installation instructions, and API references, visit the official Solana Labs repository.

https://github.com/solana-labs/solana-web3.js

The agave-watchtower program monitors cluster health by periodically polling an RPC API. It verifies that:

• Transaction counts are advancing.
• New blockhashes are available.
• No validators are delinquent.

If the Validator Admission Ticket (VAT) feature is active, it also alerts if a monitored validator's vote account balance falls below the bank-side VAT balance threshold (as visible via RPC).

Configuration Options:

• RPC URLs: Use --url to provide a single RPC URL or --urls to provide up to 3 URLs. If 3 URLs are provided, at least 2 must confirm cluster health for the check to pass. Providing exactly 2 URLs is not supported.
• Validator Filtering: Use --validator-identity to restrict failure notifications to a specific set of validators.

The Solana Virtual Machine (SVM) can be used as a standalone library outside of the standard Solana Validator. This is useful for applications such as:

• SVM Rollups: Reducing hardware requirements for rollups by executing blocks without the full validator stack.
• SVM Fraud Proofs: Generating succinct proofs of invalid state transitions.
• Validator Sidecars: Separating JSON-RPC workloads (like simulateTransaction) from the main validator.
• Custom Environments: Running SVM within other consensus frameworks (e.g., Avalanche subnets) or creating modified versions (SVM+).

The Cluster Telemetry dashboard provides visibility into the current state of the cluster, specifically covering:

1. Cluster Stability
2. Validator Streamer
3. Tomer Consensus
4. IP Network
5. Snapshots
6. RPC Send Transaction Service

The Fee Market dashboard tracks economic metrics related to transaction costs, including:

1. Total Prioritization Fees
2. Block Min Prioritization Fees
3. Cost Tracker Stats

SVMTransaction

A trait representing a transaction that has already passed protocol rule checks (e.g., signature verification and account index validation). It provides access to:

• signatures: Encrypted transaction message hashes.
• static_account_keys: Slice of Pubkey used in the transaction.
• account_keys: All account pubkeys (including address table lookups).
• recent_blockhash: The recent block hash.
• instructions_iter: Iterator over instructions.
• message_address_table_lookups: Iterator over address table lookups (for V0 transactions).

TransactionCheckResult

A data structure that stores transaction details, such as whether it contains a nonce, the nonce value, and the lamports per signature required for fees.

The Geyser Plugin Interface allows you to extend the Solana Validator runtime by injecting a plugin that reacts to real-time events, such as account updates, block processing, or transaction processing. This is commonly used to stream validator state to external storage, like a PostgreSQL database.

To create a plugin, you must:

1. Implement the GeyserPlugin trait defined in geyser_plugin_interface.rs.
2. Compile your plugin as a cdylib dynamic library.
3. Expose a C function named _create_plugin() that returns an instance of your GeyserPlugin implementation.