Introduction

Documentation is infrastructure. When systems move fast and protocols change through governance votes, knowing where to find accurate information separates competent participants from those flying blind. This chapter consolidates the essential reference materials, common clarifications, and terminology that anchor Solana’s operational reality.

Core Documents and Specs

Start with the 2017 Proof of History whitepaper. Anatoly Yakovenko authored it, and it laid out the cryptographic time-sequencing mechanism that makes parallel execution feasible without waiting for global consensus rounds. Still relevant, though the implementation evolved significantly since then.

The Solana documentation portal (docs.solana.com) provides the official developer guides, RPC endpoint specs, and architectural overviews. It’s maintained but occasionally lags behind mainnet reality—cross-check against the SIMD repository (Solana Improvement Documents on GitHub) for protocol-level changes under discussion or recently approved.

Firedancer and Frankendancer specs live in Jump Crypto’s repositories, detailing the high-performance client architecture and phased rollout plan. Agave client documentation covers the forked validator implementation post-Solana Labs archive. These aren’t casual reading, but if you’re running infrastructure or debugging performance issues, you’ll need them.

Token2022 specs outline the extended token standard—confidential transfers, programmable hooks, transfer fees at the protocol layer. State compression documentation explains how zero-knowledge proofs collapse account data into Merkle root hashes, reducing on-chain storage costs from roughly 0.0007 SOL per account to near-zero for compressed structures.

Wormhole and NTT (Native Token Transfers) docs cover cross-chain bridging mechanics. The Anchor framework documentation is essential for smart contract developers—it abstracts much of Rust’s complexity into a domain-specific language tailored for Solana programs. Sealevel concurrency guides explain how the parallel execution runtime determines transaction dependencies and schedules non-conflicting operations simultaneously.

Validator setup guides walk through hardware requirements, networking configurations, and staking mechanics. If you’re delegating rather than running infrastructure yourself, these still help you understand what validators face operationally.

Additional references worth bookmarking: staking guides that clarify activation timelines (~1 epoch delay), unbonding cooldowns (~2-3 days), and the 25% per-epoch maximum deactivation limit that prevents sudden security collapses.

Dashboards, Explorers, and Monitoring

Solana Explorer (explorer.solana.com) is the official block explorer. Functional, but Solscan (solscan.io) dominates actual usage. Etherscan acquired Solscan in early 2024, bringing institutional-grade infrastructure to Solana chain data. Solscan’s transaction summaries are clearer, the developer tools more refined, and the NFT/DeFi dashboards more comprehensive than alternatives.

Solana Beach (oklink.com/solana) displays network activity in real time—transactions per second, RPC node counts, epoch progress, slot fill rates. Economic data like circulating supply, inflation schedule, and current staking APY are updated continuously. Validator statistics show performance metrics: uptime, commission rates, vote credits earned.

SolanaFM was acquired by Jupiter in September 2024. It offered transaction diagram flows and network visualizations, though maintenance has been inconsistent since the acquisition. XRAY provides alternative chain-of-transactions visualization for tracking complex multi-step interactions.

Analytics platforms aggregate deeper metrics. DeFiLlama tracks TVL across protocols with historical charts. Token Terminal breaks down fee revenue, P/F ratios (price-to-fees), and protocol economics. Nansen and Santiment provide on-chain flow analysis—exchange deposits/withdrawals, whale movements, stablecoin velocity. Messari publishes research-grade dashboards covering activity, staking participation, and validator economics.

Jito MEV dashboards show bundle auction activity, searcher competition, and validator MEV earnings as a percentage of total rewards. These matter if you’re trying to understand what portion of validator income comes from transaction ordering rather than protocol issuance.

Monitoring infrastructure: Validator health sites track missed slots, vote participation, and software version distribution across the network. Slot and latency trackers identify performance degradation before it cascades into consensus issues. Bridge guardian status pages (Wormhole, specifically) display whether off-chain attestors are online and signing cross-chain messages. RPC status pages from major providers (Helius, Alchemy, QuickNode) show query latency and uptime.

Critical distinction: user TPS versus total TPS. Headline figures often include validator consensus votes, which comprise roughly two-thirds of transaction volume. Real user transactions—transfers, swaps, NFT mints—are lower. Check multiple sources to reconcile numbers. Similarly, distinguish compressed account activity from on-chain storage. Compressed NFT collections store only Merkle roots on-chain, with actual metadata off-chain. That affects how you interpret “NFTs minted” statistics.

FAQs and Common Clarifications

Fee structure:

Base fee is fixed at 0.000005 SOL per transaction—that’s 5,000 lamports, about half a cent at typical prices. 50% burns, 50% goes to the validator who includes it. Priority fees are optional, calculated as compute units consumed multiplied by price per unit. After SIMD-0096 passed in May 2024, 100% of priority fees go to validators (no burn). Total fee = base + priority. Most transactions cost under a penny even with priority adjustments.

Transactions don’t wait indefinitely. They expire after roughly 150 slots—about one minute. If your transaction doesn’t confirm within that window, it’s dropped. No eternal mempool like Ethereum. Resubmit if you need it processed.

Staking mechanics:

Activation takes about one epoch (approximately 2-3 days, depending on slot timing). Your staked SOL doesn’t earn rewards immediately—it activates at the next epoch boundary, then begins accruing. Deactivation also takes one epoch. You can initiate unstaking anytime, but the SOL remains locked for that cooldown period before becoming liquid again. Maximum 25% of total active stake can deactivate per epoch network-wide. That’s a protocol-level safety mechanism preventing sudden validator exodus.

Rewards compound automatically at epoch boundaries. No manual claiming required. Just stake, wait, watch it grow (or shrink, if your validator underperforms or gets slashed—though slashing hasn’t been activated in practice yet).

MEV on Solana:

Primarily private order flow routed through Jito bundles. Validators running Jito-Solana software (65%+ of the network as of early 2025) accept bundle submissions from searchers who bid for transaction inclusion and ordering. Jito shares rebates with validators. Proposer-Builder Separation isn’t live yet—it’s being researched, but the current model is validator-controlled MEV extraction with Jito as intermediary infrastructure.

Front-running happens differently than Ethereum. No public mempool to observe pending transactions. Instead, transactions get forwarded to the scheduled leader via Gulf Stream protocol before the leader’s slot begins. Latency matters. If you’re colocated with leaders or have low-latency RPC connections, you observe transactions earlier. That’s the MEV edge. Fairness depends on connectivity and infrastructure placement, not transaction gas auctions.

Gulf Stream and mempool misconceptions:

Solana doesn’t have a public mempool. Transactions route directly to slot leaders (current and next two in the schedule). Leaders process them in real time during their assigned slots. If a transaction doesn’t land in those slots, it expires. This eliminates the traditional front-running window where attackers monitor a shared pool, but it creates new MEV vectors through leader proximity and private RPC endpoints.

State compression:

On-chain roots, off-chain data. Compressed accounts store a Merkle tree root hash on-chain, with the actual account data living in off-chain storage (specialized RPC nodes, IPFS, Filecoin, or application-managed databases). To verify an account’s existence and state, you provide a zero-knowledge proof against the on-chain root. This drastically reduces per-account storage costs—millions of NFTs or loyalty points can exist as a single root hash rather than individual on-chain accounts.

Trade-off: you need off-chain infrastructure to retrieve the data. If that infrastructure fails or censors, the data becomes inaccessible even though the root hash remains on-chain. It’s a scaling solution, not a pure decentralization win.

Glossary Touchpoints

Proof of History (PoH): Cryptographic time-sequencing mechanism using recursive SHA-256 hashing to create verifiable passage of time without relying on external clocks. Validators compute PoH chains continuously, proving events occurred in a specific order.

Tower BFT: Solana’s consensus algorithm—an optimized variant of Practical Byzantine Fault Tolerance. Uses lockout mechanisms where validators commit stake with increasing time weights, making equivocation (voting on conflicting forks) economically punishable.

Sealevel: Solana’s parallel transaction execution runtime. Unlike Ethereum’s single-threaded EVM, Sealevel runs non-conflicting transactions simultaneously across multiple CPU cores by analyzing read/write dependencies declared explicitly in transactions.

Turbine: Block propagation protocol that breaks blocks into small chunks (shreds), applies erasure coding for redundancy, and distributes them across the network. Validators can reconstruct full blocks even if some shreds are lost during transmission.

Gulf Stream: Transaction forwarding mechanism that routes transactions to current and upcoming slot leaders before their slots begin. Eliminates traditional mempool by delivering transactions directly to leaders, reducing confirmation latency.

SVM rollups: Layer 2 scaling solutions using the Solana Virtual Machine for execution but settling back to Solana (or potentially other L1s like Ethereum). Lollipop framework enables developers to deploy SVM-based rollups for specialized workloads—gaming, high-frequency DeFi, NFT minting bursts—without congesting mainnet.

Token2022: Extended token standard adding features like confidential transfers (hiding amounts using homomorphic encryption), transfer hooks (programmable logic triggered on token movements), and protocol-level transfer fees. Designed to enable compliant institutional use cases without sacrificing on-chain functionality.

State compression: Technique using zero-knowledge proofs and Merkle trees to store millions of accounts as a single on-chain root hash, with data living off-chain. Drastically reduces storage costs for applications with large user bases (gaming, loyalty programs, compressed NFT collections).

VAAs (Verifiable Action Approvals): Wormhole’s cross-chain message format. Off-chain guardian nodes attest to events on one chain, producing cryptographically signed messages that other chains verify. Enables asset bridging and cross-chain communication without requiring on-chain light clients.

NTT (Native Token Transfers): Wormhole standard allowing tokens to exist natively on multiple chains rather than as wrapped representations. Improves user experience by eliminating the wrapped/native distinction that confuses participants and fragments liquidity.

SIMD governance: Solana Improvement Documents—the formal proposal process for protocol changes. Technical specs, economic adjustments, and governance votes happen through SIMD submissions on GitHub, followed by validator voting weighted by stake.

Winternitz vaults: Hash-based signature scheme providing quantum resistance. Users generate new keys per transaction, making coordinated quantum attacks harder. Currently optional—requires explicit migration, not network-wide enforcement. Whether it scales to full ecosystem adoption remains an open question.

Priority fees: Optional fees paid to increase transaction priority during congestion. Calculated as compute unit limit multiplied by price per unit. After SIMD-0096, 100% flows to validators (previously split 50/50 with burn). Gives users control over confirmation speed when the network is saturated.

Jito/MEV infrastructure: Jito-Solana client enables validators to accept bundle submissions from MEV searchers. Block Engine (off-chain auction system) coordinates bids. Searchers compete for transaction ordering, validators earn additional revenue beyond protocol issuance. Represents structured MEV extraction rather than ad-hoc front-running.

Agave/Firedancer/Frankendancer: Validator client implementations. Agave is the community-maintained fork post-Solana Labs archive. Firedancer is Jump Crypto’s high-performance rewrite demonstrating over one million TPS in controlled tests. Frankendancer is the hybrid prototype combining Firedancer components with existing infrastructure for phased mainnet rollout.

TPU (Transaction Processing Unit): Multi-stage pipeline within validators handling transaction ingestion, signature verification, execution, and broadcast. Stages include Fetch, SigVerify, Banking, and Broadcast. Optimizing TPU throughput is central to validator performance.

Compressed accounts: Accounts stored as Merkle tree leaves with only the root hash on-chain. Data retrieved off-chain via proofs. Enables applications to scale beyond what’s economically feasible with traditional on-chain accounts (which require rent-exempt minimums).

Travel Rule: Regulatory requirement (FATF recommendation, EU MiCA enforcement) mandating that wallet providers collect and transmit customer information for transfers above certain thresholds (e.g., €1,000 in EU). Affects institutional stablecoin usage on Solana—compliance layers being built into protocols to satisfy these mandates.

MiCA (Markets in Crypto-Assets): EU regulatory framework governing stablecoins, crypto service providers, and market integrity. Took effect December 30, 2024. Major impact on Solana: Tether (USDT) deemed non-compliant and delisted from EU exchanges. Circle’s USDC and other licensed stablecoins remain compliant, shifting ecosystem liquidity.

These definitions aren’t exhaustive. Solana’s terminology evolves as protocol upgrades ship and governance decisions reshape economic parameters. Treat this as a snapshot, not scripture.