Research draftNot RatedRank #7 · CoinGecko snapshotLayer 1
SO

Solana (SOL) review

Tokenomics, security and network risks

SOL has direct fee and staking utility, while inflation, dominant Agave-family stake, past coordinated restarts, and unresolved market and ownership evidence keep this draft Not Rated.

Research view, not a price call. This report describes evidence and uncertainty. It is not personalized investment advice.
Verdict & confidence

What the evidence supports today

Research conclusionNot Rated

Core protocol mechanics are observable, but executable market depth, beneficial-owner and hosting concentration, and independently reconciled client share are still missing. Layer North does not convert those unknowns into a score.

Evidence confidenceLow

Direct utility is observable

Observed

Every transaction pays a fee in SOL, and delegated SOL participates in the network's stake-weighted validator system.

Layer North view: SOL has functional protocol demand. That is stronger than a purely promotional utility claim, but it does not prove that network activity will translate into investment returns.

S01S02

Critical categories remain open

Unresolved

This review does not yet have standardized executable depth, beneficial-owner mapping, current hosting concentration, or a fully reconciled client-by-stake classification.

Layer North view: Market liquidity and decentralization cannot be responsibly reduced to Low or Moderate risk while these measurements are absent.

S05S06S15

Client diversity is in transition

Qualified

The live estimate placed 85.61% of active stake in the Agave/Jito family, 11.52% in Frankendancer's hybrid client and 2.82% in full Firedancer.

Layer North view: Full Firedancer is now mainnet-ready software, but it is new and still a small share of stake. Advertised versions are not cryptographic proof of the binary being run.

S05S06S13
Dated observations

Snapshot, not a live ticker

Each value is tied to a named source and observation date. Market rank is context—not a quality score.

Market-cap rank#7

CoinGecko provider snapshot. Rank can differ by provider and inclusion rules.

As of 11 Aug 2026 S16
Total supply632.01M SOL

632,009,538.163349009 SOL from finalized mainnet state at slot 438,619,685.

As of 11 Aug 2026 14:02 UTC · slot 438,619,685 S03S21
Circulating supply582.48M SOL

RPC classification; it is not a measure of beneficial ownership or freely tradable float.

As of 11 Aug 2026 14:02 UTC · slot 438,619,685 S03S21
Protocol inflation3.7016%

Total and validator inflation rate returned for epoch 1015; not the same as staking yield.

As of 11 Aug 2026 14:02 UTC · epoch 1015 S04S21
Active validator stake434.90M SOL

Across 691 current vote accounts. Vote accounts do not necessarily equal distinct operators.

As of 11 Aug 2026 14:02 UTC S05S21
Full Firedancer stake2.82%

Nine current validators advertised full Firedancer versions; version strings are self-reported.

As of 11 Aug 2026 14:02 UTC S05S06S13S21
Identity & scope

What Solana is—and what this review covers

The review evaluates the native SOL asset and Solana's base network. It does not treat every wallet, bridge, application or SPL token incident as a base-protocol event.

SOL is native, not an SPL project token

Supported

Native SOL pays transaction fees and funds stake accounts. It has no project-token contract address; wrapped SOL is a token representation with a separate mint identity.

Layer North view: Readers should verify the asset and network before transfer. A token using SOL in its name is not automatically native SOL.

S01S02

A stake-weighted validator network

Supported

Validators process transactions and vote on the chain, while holders can delegate stake to validators. Current network behavior should be distinguished from roadmap consensus changes.

Layer North view: Stake supports consensus participation; it is not a promise that the network cannot halt or that delegated capital cannot lose market value.

S02S18
Tokenomics

Supply and inflation are observable—but not fixed forever

The configured schedule, current protocol rate, realized supply change and a holder's economic dilution are related but different measures.

No fixed maximum supply

Observed

The queried inflation governor uses an 8% initial rate, a 15% annual taper and a 1.5% terminal rate. The live total inflation rate was 3.7016076109% at epoch 1015.

Layer North view: The current rule path is inflationary. Future parameter changes require governance, implementation and activation; proposals must not be presented as current policy.

S02S04

Staking yield is not the inflation rate

Supported

A delegator's result also depends on the fraction of SOL staked, validator performance, commission and the holder's own custody and liquidity choices.

Layer North view: Staking may offset part of supply-share dilution, but it does not remove price, validator, custody or liquidity risk.

S02S05
Fees & value capture

Follow the SOL: who pays, who earns and what burns

Network activity matters only after tracing where value actually flows. Application revenue and SOL-holder value are not interchangeable.

Base fees partly burn; priority fees pay validators

Observed

The documented base fee is 5,000 lamports per signature, split 50% burned and 50% to the validator. The optional priority fee is paid entirely to the validator.

Layer North view: The burn creates usage-linked supply reduction, but only for the base-fee portion. Gross issuance can remain larger than burned fees.

S01

Application success does not automatically accrue to SOL

Qualified

SOL is required for protocol fees and staking, while applications can retain their own fees, issue separate tokens or direct revenue to other participants.

Layer North view: High transaction counts alone do not establish durable token value capture. Fee mix, issuance, burn and economically meaningful demand must be measured together.

S01S07
Decentralization evidence

Stake, operators and software clients are separate concentration questions

Address-level measurements are useful but do not reveal common ownership, shared infrastructure or independent code paths by themselves.

Vote-account concentration is measurable

Observed

Across 691 current accounts, the top vote account held 3.9063% of active stake, the top five 15.3939%, the top ten 24.3700%, and 18 vote accounts crossed 33.34%.

Layer North view: This is a vote-account superminority measure, not an entity-level Nakamoto coefficient. One operator can control several accounts, so ownership and hosting remain unresolved.

S05S21

Validator operation has a meaningful resource floor

Supported

Anza recommends 12 cores/24 threads, 256GB or more RAM, multiple NVMe drives and at least 2 Gbit/s symmetric bandwidth for a staked validator; voting can consume SOL.

Layer North view: These requirements can raise operating and geographic barriers, although they are recommendations rather than a protocol-level minimum hardware specification.

S08

Independent-client adoption is real but early

Qualified

The stake-weighted estimate was 85.6141% Agave/Jito, 11.5160% Frankendancer hybrid, 2.8166% full Firedancer and 0.0534% unknown.

Layer North view: The estimate maps self-reported versions to client families. It cannot separate vanilla Agave from Jito or attest to the exact running binary, and full Firedancer has a short mainnet history.

S05S06S13S21
Control map

Protocol change combines public proposals, implementation and stake

Calling governance simply on-chain or informal misses how Solana changes actually move from an idea to running code.

SIMDs document technical change; they do not deploy it

Supported

The public SIMD process records proposed and accepted protocol changes. A proposal still requires implementation, release and network activation before it describes current behavior.

Layer North view: Roadmap claims should carry a lifecycle label such as Draft, Review, Accepted, Released or Activated.

S10

New governance can trigger stake-weighted votes

Supported

The SGP process says default decision-making remains with core developers and the SIMD process; support from 15% of active stake can trigger a three-epoch on-chain directional vote.

Layer North view: Practical control spans authors, maintainers, client teams, validators and stake—not SOL holders through one universal voting mechanism.

S11S12

Foundation delegation is visible but partial

Qualified

The Foundation dashboard reports its delegation-program validators, stake, locations and countries, while its criteria explicitly address data-center and ASN concentration.

Layer North view: These figures describe one program, not the full network. They cannot replace a current all-validator hosting and entity map.

S15
Security boundaries

Base-network risk is not every Solana ecosystem exploit

Consensus, validator clients, RPC infrastructure, on-chain applications, bridges, wallets and malicious tokens have different failure modes.

A public validator security process exists

Supported

The Agave repository documents private vulnerability reporting, incident response and bug-bounty categories covering loss of funds, consensus safety, liveness and denial of service.

Layer North view: A disclosure process is a control, not proof that the code is defect-free or that every ecosystem component shares the same process.

S17

A 2025 critical flaw was patched before disclosure

Supported

A ZK ElGamal proof flaw could have enabled unauthorized actions in affected Token-2022 confidential tokens. The Foundation says Anza, Firedancer and Jito prepared patches, a supermajority adopted them before disclosure, and no known exploit occurred.

Layer North view: This is evidence of effective response and evidence that critical native-program flaws can exist. Emergency confidentiality also creates temporary reliance on trusted coordination.

S22

Scope incidents before drawing conclusions

Supported

An application exploit or wallet compromise can affect Solana users without breaking consensus or halting block production.

Layer North view: Layer North will classify incidents by affected layer rather than using an undifferentiated 'Solana hacks' count.

S09S17
Reliability record

Past coordinated restarts and recent uptime both matter

A useful record separates consensus halts, degraded performance and public RPC incidents, then shows the recovery mechanism and remediation.

6 February 2024: mainnet stopped finalizing

Supported

Solana's official report says block finalization stopped and validator operators coordinated a restart using patched v1.17.20 software.

Layer North view: The incident demonstrates a material liveness and coordination risk. A restart is recovery evidence, not evidence that the halt was immaterial.

S09

The recent official window is materially better

Observed

The official status page showed 100% Mainnet Beta cluster uptime over its latest 90-day window at the review cutoff.

Layer North view: Recent improvement counters a claim that outages are currently frequent, while the historical restart record remains relevant to stress analysis.

S19
Market evidence

Rank, availability and liquidity are not the same thing

A large market capitalization and many listed venues do not establish the price available for a large real order during normal or stressed conditions.

Market liquidity remains Not Rated

Unresolved

Layer North has not yet collected standardized spread, depth at ±0.5%/1%/2%, $100k and $1m slippage, venue concentration and stress-window withdrawal evidence.

Layer North view: The previous Low risk label has been removed. Reported volume and rank cannot substitute for executable depth.

S16

Price volatility is directly measurable

Observed

Across 366 daily USD observations from 12 August 2025 through 11 August 2026, the audit calculated 69.85% annualized daily log-return volatility and a −74.89% maximum drawdown.

Layer North view: This supports a High price-volatility label for the stated window. It does not predict the next year's return or establish which factor caused past moves.

S20
Risk register

Material risks and reassessment triggers

Impact labels are editorial judgments, not forecasts of price direction. Unsupported likelihood estimates remain unrated.

Executable market liquidity

Unresolved
ImpactUnratedTrendUnknown

Venue listings and reported volume do not show executable depth or stress slippage.

Reassess when: standardized spread, depth, slippage, venue-concentration and withdrawal tests are completed

S16

Client common-mode failure

Qualified
ImpactHighTrendImproving

Alternative client work is shipping, but full independence and current mainnet stake share are not yet reconciled.

Reassess when: independent codebases gain or lose material stake, or a client defect affects finalization

S13S14

Stake and infrastructure concentration

Qualified
ImpactHighTrendUnknown

Vote-account concentration is reproducible, while entity ownership, hosting and geographic common control remain incomplete.

Reassess when: the 33.34% set changes materially or an entity/hosting map is completed

S05S15

Supply dilution

Observed
ImpactModerateTrendStable

The protocol remains inflationary; staking rewards and base-fee burn offset different parts of gross issuance but do not create a fixed cap.

Reassess when: inflation or fee-distribution rules activate, or realized net issuance diverges materially from the schedule

S01S02S04

Network liveness and coordination

Supported
ImpactHighTrendImproving

The network has required coordinated restarts, while the latest official 90-day uptime window is 100%.

Reassess when: a mainnet halt, material degradation or restart occurs

S09S19

Protocol-upgrade governance

Qualified
ImpactHighTrendUnknown

Public proposal and stake-vote processes improve visibility, but implementation and activation remain concentrated coordination points.

Reassess when: a major fee, inflation or consensus change moves from proposal to activation

S10S11S12

Price volatility

Observed
ImpactHighTrendUnknown

The measured one-year drawdown and annualized volatility are severe even for a widely traded cryptoasset.

Reassess when: the standardized 30/90/365-day volatility and drawdown bands cross the published rubric

S20
Investment framework

Is SOL a good investment? Evidence to test, not a recommendation.

The report does not issue a price target. It shows the observations that support the case, the countercase, and the signals that could change either.

Supporting evidence
  • SOL has direct protocol utility for fees and stake delegation.
  • Supply, inflation and validator stake are observable through public mainnet RPC methods.
  • The official recent-uptime window is materially stronger than the 2022–2024 outage narrative alone suggests.
  • Alternative validator-client development is active and mainnet hybrid releases exist.
Countercase
  • Positive issuance dilutes an unstaked holder's share unless offset by other economics.
  • Application revenue and transaction counts do not automatically accrue to SOL holders.
  • Client, entity and hosting common-mode risks are incompletely measured.
  • Past halts, upgrade coordination and severe market drawdowns remain material risks.
Monitor / falsify
  • Net issuance after fee burn and the share of validator economics funded by issuance.
  • Stake share by genuinely independent production client—not version label alone.
  • Vote-account, entity, ASN, data-center and geographic concentration.
  • Executable depth and slippage during both normal and stressed markets.
  • Activation outcomes for material consensus, fee and inflation proposals.
Evidence log

Claim-to-source record

Primary records establish documented rules and project-reported status. Dated measurements add observable context; neither substitutes for independent market, legal, or counterparty evidence.

S01
Solana fee mechanicsSolana · Protocol documentation · accessed Aug 11, 2026Fee requirement, base fee, burn split and priority-fee destination.
S02
Staking and inflation FAQSolana · Protocol documentation · accessed Aug 11, 2026Staking roles, reward factors and configured inflation schedule.
S03
getSupply RPC methodSolana · On-chain observation · accessed Aug 11, 2026Finalized total and circulating supply at slot 438,618,523.
S04
getInflationRate and governor RPC methodsSolana · On-chain observation · accessed Aug 11, 2026Epoch-1015 inflation rate and live governor parameters.
S05
getVoteAccounts RPC methodSolana · On-chain observation · accessed Aug 11, 2026Active stake, vote-account count and stake-concentration calculations.
S06
getClusterNodes RPC methodSolana · On-chain observation · accessed Aug 11, 2026Raw validator version strings joined to vote-account stake.
S07
getRecentPerformanceSamples RPC methodSolana · On-chain observation · accessed Aug 11, 2026Five-minute observed transaction-load sample; not a capacity claim.
S08
Agave validator requirementsAnza · Protocol documentation · accessed Aug 11, 2026Recommended compute, memory, storage, bandwidth and voting-cost requirements.
S09
6 February 2024 Mainnet Beta outage reportSolana · Status record · accessed Aug 11, 2026Halt scope, coordinated restart and patched validator release.
S10
Solana Improvement DocumentsSolana Foundation · Repository · accessed Aug 11, 2026Public protocol-proposal process and lifecycle.
S11
Solana governance documentationSolana Foundation · Protocol documentation · accessed Aug 11, 2026Stake-weighted governance mechanics and delegator participation.
S12
Solana Governance ProposalsSolana Foundation · Repository · accessed Aug 11, 2026Relationship between default SIMD decision-making and triggered stake votes.
S13
Firedancer releasesFiredancer · Repository · accessed Aug 11, 2026Mainnet-ready full Firedancer releases and Frankendancer hybrid distinction.
S14
Solana changelog, 16 July 2026Solana Foundation · Status record · accessed Aug 11, 2026Dated Agave, Firedancer testnet and Frankendancer mainnet release status.
S15
Foundation delegation dashboard and criteriaSolana Foundation · Protocol documentation · accessed Aug 11, 2026Foundation-program scope, delegated stake and concentration criteria.
S16
Solana market pageCoinGecko · Market data · accessed Aug 11, 2026Provider-specific market-cap rank; not used as executable-liquidity evidence.
S17
Agave security policyAnza · Repository · accessed Aug 11, 2026Vulnerability reporting, incident response and bug-bounty scope.
S18
Solana core conceptsSolana · Protocol documentation · accessed Aug 11, 2026Accounts, programs, transactions and current network concepts.
S19
Solana public statusSolana · Status record · accessed Aug 11, 2026Latest 90-day Mainnet Beta cluster uptime window.
S20
Solana historical daily market dataCoinGecko · Market data · accessed Aug 11, 2026366-observation USD volatility and maximum-drawdown calculation.
S21
Mainnet RPC audit snapshotLayer North Research / Solana mainnet · On-chain observation · accessed Aug 11, 2026Batch begun 2026-08-11 14:02:03 UTC: requests, exact scalar outputs, derived stake concentration and client-family estimates.
S22
ZK ElGamal proof program postmortemSolana Foundation · Status record · accessed Aug 11, 2026Vulnerability scope, coordinated patch adoption and no-known-exploit statement.
Research record

Limitations, disclosures and change log

Known limitations

  • No named analyst or independent reviewer has signed this draft.
  • Market depth, slippage and stress-liquidity measurements are not yet available.
  • Vote accounts have not been fully resolved to beneficial owners or shared operators.
  • Client version strings have not been completely mapped to independent codebases by stake.
  • The public incident record may omit degradations that did not halt finalization.
  • RPC and market observations are dated snapshots and do not update live on this page.

Report disclosure

Sponsorship
No project sponsorship is shown on this draft; operator attestation is pending before publication.
Affiliate links
No affiliate links appear in this report.
Holdings
Named author and reviewer holdings attestations are pending.
Automation
Automation assisted source collection and calculations; named human verification and sign-off are pending.
Aug 11, 2026v0.2

Expanded the pilot into a claim-level evidence draft; corrected rank #5 to provider-specific rank #7; added RPC, fee, inflation, validator, governance, client and incident evidence; removed the unsupported overall and liquidity conclusions.

Aug 11, 2026v0.1

Initial two-source pilot skeleton. Retained in the log for transparency; it did not pass the publication gate.