The Vault Liquid Staking

Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.

The Vault issues vSOL against SOL deposited into a Solana stake pool. Current documentation describes a layered delegation policy rather than only the older community-validator allowlist: 40% follows a direct-stake leaderboard, 50% targets a performance-elite set, and 10% is directed by veV gauge voting that may be incentivized. That design combines validator performance, governance and economic influence in a strategy the protocol can change. DefiLlama recorded about $102M at the 2026-08-14 survey, above the program’s materiality floor. The standard stake-pool mechanism and documented delayed-withdrawal path are useful evidence, but the current authority map, allocation-change history, live validator concentration, vSOL liquidity under stress and a vSOL-specific security record are not complete enough for institutional underwriting. Rejected on the missing record, not on an allegation of loss or misconduct.

Kill criteria: the events that revoke this verdict
• Current program, upgrade and emergency authorities are disclosed and reconciled to deployed accounts
• Allocation and approved-validator change history plus validator-level stake and performance data are reproducible
• vSOL-specific audits, dependency inventory, bug-bounty status and incident history are complete
• vSOL demonstrates delayed redemption and secondary liquidity at the contemplated client size under network stress
• Gauge-vote concentration and incentive dependence are quantified against the selected Solana LST

The research file

Mechanism and return source

A depositor contributes SOL and receives vSOL, whose SOL exchange rate increases as delegated stake earns validator rewards. The pool uses Solana’s stake-pool program; the economic return is native staking yield net of pool economics, while the holder inherits validator performance, stake-pool-program and integration risk. Validator-specific LSTs can also wrap vSOL, adding another token and liquidity layer rather than changing the underlying return source.

Delegation policy and control

Current protocol documentation allocates 40% to validators leading the direct-stake program, 50% to a performance-elite set, and 10% through veV gauges. The gauge layer permits voters to direct stake and permits validators or communities to incentivize votes. Approved-validator and stakebot rules include performance, commission, uptime and good-actor screens, with automated updates described every three hours. These are observable rules, but the reviewed public record does not yet provide a complete authority matrix, immutable limits or a reproducible history of strategy and allowlist changes.

Security and incident record

The Vault states that vSOL uses Solana’s audited SPL stake-pool program and identifies Quarry, Sanctum and Saber as dependencies with their own reviews. That is dependency evidence, not a vSOL-specific audit or an independently verified no-incident conclusion. No disclosed vSOL loss was located in the reviewed primary materials, but absence from those pages is not evidence that no incident occurred. Approval therefore requires a scoped contract and authority inventory, current audits, bug-bounty status and a reconciled incident history.

Exit and liquidity

The documented delayed withdrawal returns a stake account and may require waiting until the next epoch, described as up to roughly three days. An instant exit is instead a market sale of vSOL and can incur price impact or a discount to intrinsic value; the protocol also documents a command-line withdrawal path independent of its web application. The existence of two paths is constructive, but it does not establish executable depth for an advised sleeve or performance during congestion and validator stress.

Comparison and decision

A Solana LST suitable for client assets must make validator allocation reproducible, disclose who can change the policy, and demonstrate primary and secondary exits at the proposed position size. The Vault’s layered policy is more specific than the former mission-only description, but gauge incentives and mutable strategy add governance questions while the liquidity and security record remain incomplete. The selected-category benchmark is not displaced until those differences can be measured against a fully underwritten Solana LST.

Observable reopening conditions

Reopen after the protocol publishes the current program and upgrade authorities, allocation and allowlist change history, validator-level stake and performance data, and scoped security reviews; then test vSOL redemption and secondary-market depth at the contemplated client size. The review should also quantify gauge-vote concentration and incentives, reconcile any incident history, and compare stressed epoch withdrawal with the selected Solana LST. These are evidence gates, not a requirement that TVL alone increase.

Sources

The claims above trace to these. Where a number could not be independently verified, the thesis says so.

• The Vault Docs — vSOL mechanism · primary · accessed 2026-08-14
  Supports: vSOL receipt, exchange-rate accrual, staking rewards
• The Vault Docs — delegation overview · primary · accessed 2026-08-14
  Supports: 40 percent direct stake, 50 percent performance elite, 10 percent gauges, strategy changes
• The Vault Docs — gauges · primary · accessed 2026-08-14
  Supports: veV voting, gauge incentives, validator eligibility
• The Vault Docs — approved validators · primary · accessed 2026-08-14
  Supports: stakebot cadence, validator screens, allocation buckets
• The Vault Docs — protocol and liquidity risks · primary · accessed 2026-08-14
  Supports: SPL stake pool, protocol dependencies, market-price risk, delayed withdrawal, CLI exit
• The Vault Docs — validator LST creator · primary · accessed 2026-08-14
  Supports: validator-specific LST, vSOL wrapper, unstaking fee
• DefiLlama — The Vault survey record · secondary · accessed 2026-08-14
  Supports: survey TVL, chain, liquid-staking category

Inherited controls

The verdict above grades the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The least safe layer sets the position’s grade, and the position table names which one that is.