Solana Explained: SOL, Network Fees, Staking and Upgrade Risks

What Solana is, and where SOL fits

Solana is a public blockchain designed for applications that need frequent transactions and short waits. Its native asset, SOL, pays network fees and supports the proof-of-stake system used to agree on the ledger. Payments, trading applications, games and digital collectibles can all use the same underlying network.

SOL is different from the many tokens issued on Solana. Owning one of those tokens does not mean owning SOL, and an application using Solana does not inherit a guarantee of safety from the network. The live market panel above follows SOL itself.

As of October 8, 2026, Solana remains an active network with protocol upgrades in progress. Some performance improvements have shipped, while its proposed Alpenglow consensus system is still listed as in development. Understanding that boundary matters when reading claims about transaction speed.

The project's origins and the organizations behind it

Anatoly Yakovenko authored Solana's original white paper, which explored a way to establish the ordering of events through a cryptographically verifiable sequence. That idea, called proof of history, became a central part of the network's original architecture.

The Solana Foundation's 2020 review records the mainnet beta launch in March of that year. The network expanded around validators, application teams and open-source contributors rather than a single application. Its early development also introduced the token and program infrastructure on which later applications were built.

The Solana Foundation is a nonprofit based in Zug, Switzerland. It supports work on adoption, decentralization and security, including grants and validator delegation. Those activities are distinct from a validator's job of processing transactions and participating in consensus. Users should likewise distinguish the foundation, software-development teams and independent businesses built on the chain.

Proof of stake, proof of history and program execution

Solana uses stake-weighted consensus. Validators vote on blocks, and the amount of stake assigned to a validator influences the weight of its vote. SOL holders can delegate to a validator without handing that validator ownership of their tokens.

Proof of history addresses a different problem: establishing a verifiable ordering and passage of time. It is a sequence of computations that other participants can check. It should not be described as a replacement for proof of stake, because ordering events and agreeing which history to accept are related but distinct tasks.

Applications execute through programs, Solana's term for smart contracts. Program code and changeable application data are held in separate accounts. Transactions specify instructions and the accounts involved. This design supports an execution model in which suitable work can be processed in parallel, although transactions competing to change the same data cannot simply ignore one another.

For readers comparing different approaches to proof of stake, our Cardano profile provides a separate example. Sharing a broad consensus category does not make two networks interchangeable: their transaction models, delegation rules and software differ.

Fees and speed require more than one number

Solana's fee documentation, checked on October 8, 2026, specifies a base fee of 5,000 lamports per signature. A lamport is a small unit of SOL. Transactions may also include a prioritization fee to improve their scheduling priority when they compete for processing.

The fee rules divide the base fee equally between burning and payment to the validator. Prioritization fees go to the validator. This is why saying that half of every Solana transaction fee is burned would be inaccurate: the components have different treatment.

A transaction's total cost can also involve application charges or funding an account, which should not be confused with the network fee itself. Check the complete wallet request, including any amounts transferred to an application. A low base fee does not make every possible interaction equally cheap.

Speed has several meanings. The interval between scheduled slots, the time before a user sees a confirmation, and finality are different measurements. A wallet updating quickly is useful, but it is not sufficient evidence that every settlement condition has been met.

On October 8, the official upgrade tracker described slot-time reductions as partially activated and Alpenglow as in development. The latter targets roughly 150-millisecond finality, but that is a development target rather than a measurement of a fully deployed system. This profile therefore does not present it as current user performance.

SOL issuance and what staking rewards represent

SOL has ongoing issuance rather than a fixed maximum supply. The inflation schedule documented by the project begins at an annualized 8%, reduces that rate by 15% per year, and approaches a long-term annual rate of 1.5%. The 8% figure describes the initial schedule, not the inflation rate on the date of this profile.

A 15% reduction in the rate means a relative reduction, not a subtraction of 15 percentage points. For example, reducing an illustrative 4% rate by 15% produces 3.4%. This arithmetic example explains the mechanism and is not a claim about the current rate.

New issuance supports validator and delegator rewards. Burning removes some SOL, so net supply change depends on more than the issuance schedule alone. The market panel's supply data should be read as a dated measurement rather than as a permanent ceiling.

Staking yield is also different from inflation. The share of SOL staked, validator performance and commissions affect what a delegator receives. Native stake must pass through activation and deactivation states, so unstaking is not necessarily an immediate withdrawal. A liquid-staking token introduces another asset and another set of contracts or service arrangements.

Our guide to how people earn cryptocurrency puts staking rewards alongside their costs and risks. Receiving more tokens does not ensure that their total market value has increased.

Tokens on Solana have their own rules

Solana's token programs support fungible assets and non-fungible assets. A mint account identifies a token and records important information, including supply and relevant authorities. A token account records ownership associated with that mint.

Those authorities matter. A retained mint authority may be able to create additional units, while a freeze authority may be able to restrict transfers from token accounts. The presence, absence and control of these permissions should be checked for the particular asset. A familiar ticker or image is not enough to establish identity.

This becomes especially important for payment assets. A stablecoin on Solana introduces the issuer's reserve and redemption arrangements alongside network risk. Our Tether profile explains why the blockchain carrying a token and the organization responsible for its backing answer different questions.

Upgrades have to be separated from promises

The official upgrade tracker lists Agave 4.2 as shipped in August 2026. It identifies larger transaction sizes as live while describing reductions in storage funding requirements and slot times as only partially activated. A software release can therefore contain changes at different deployment stages.

That is a useful way to read Solana's development more broadly. A proposal, a client implementation and an activated network feature are different milestones. An advertised improvement should be evaluated against its actual status and its effect on the application a person uses.

History also shows why reliability belongs beside speed. In its report on February 6, 2024, Anza documented a software bug that stopped block finalization. Validators coordinated a patched restart, and consensus progress resumed after an incident lasting approximately five hours. This is a dated event, not a claim that the network is currently halted.

The main risks for a SOL user

SOL's market price can move sharply. Staking does not remove that exposure, and an application can fail even when the base network continues operating. Some programs remain upgradeable through an authority, which creates a separate question about who can change their behavior.

Operational risk includes software faults, delays and concentration of influence among validators. Because consensus votes are weighted by stake, counting validators alone cannot show how voting power is distributed. The 2024 incident also demonstrates why shared software dependencies can matter.

Finally, self-custody puts signing decisions in the user's hands. Fake support messages, imitation applications and unsolicited tokens can lead to harmful transactions. Protect the recovery phrase, confirm the intended network and recipient, and understand the permissions being approved. Low fees make experimentation easier, but they do not make an incorrect or malicious instruction harmless.