Starke Staked SOL

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

Starke Staked SOL is the rkSOL liquid-staking token on Solana: SOL is delegated to the Starke validator and rkSOL appreciates as staking rewards accrue. The 2026-08-16 DefiLlama observation was about $0.82M, under one percent of our $100M materiality floor. A venue this small cannot take advised client money without the client dominating the pool: one practice advising 100 households moves $1M to $8M into a venue on the same research. The file is rejected on size. The single-validator concentration, unverified proposed-size native redemption and absence of a pinpoint current audit and authority package would remain separate blockers even if rkSOL crossed the size floor.

Kill criteria: the events that revoke this verdict
• TVL sustained above $100M for 30 days
• Publishes current program authorities, audit scope, reserve reconciliation, realized validator allocation, and a proposed-size native redemption test

The research file

Mechanism applicability

Starke describes rkSOL as a Solana liquid-staking token issued when SOL is staked with the Starke validator. The token amount remains constant while its SOL exchange value accrues epoch rewards; it can also be transferred or used elsewhere in DeFi. This is a genuine staking receipt rather than a lending, LP or delegated-strategy claim, but it concentrates the underlying stake with one named validator.

Current observation and perimeter

The DefiLlama protocol API read on 2026-08-16 classified Starke Staked SOL as Liquid Staking and reported approximately $0.82M, entirely on Solana. Starke identifies the rkSOL mint address as EPCz5LK372vmvCkZH3HgSuGNKACJJwwxsofW6fypCPZL and says the product launched on 2024-05-29. Its January 2026 validator report said rkSOL represented 27.86% of Starke validator active stake; that is issuer reporting, not independently verified diversification evidence.

Control, loss and exit applicability

Starke states rkSOL was engineered with Sanctum and uses a single-validator stake-pool program, but the reviewed product pages do not map the currently deployed program authority, upgrade and pause roles, a current audit report, reserve reconciliation, or the exact native SOL redemption queue. Transferability and possible DEX use do not prove that a proposed-size exit can redeem at net asset value during validator or secondary-market stress.

Why the class rule decides

At approximately $0.82M, a $1M advised allocation would exceed the measured product before validator concentration, authority, audit and redemption risks are underwritten. No approved Solana LST supplies a category-reviewed substitute, so the shared version-1 below-materiality dossier remains the exact deciding basis rather than a forced category selection. Reopen only after measured TVL remains above $100M for 30 days and primary or on-chain evidence identifies authorities, audit scope, reserve backing, realized validator allocation and a proposed-size native redemption.

Sources

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

• Starke — rkSOL product and token identity · primary · accessed 2026-08-16
  Supports: rkSOL, mint address, single-validator pool, reward accrual, liquidity, Solana
• Starke — native and liquid staking mechanism · primary · accessed 2026-08-16
  Supports: Starke validator, rkSOL receipt, staking rewards, native cooldown, liquid staking
• Starke — September 2025 rkSOL report · primary · accessed 2026-08-16
  Supports: launch date, SOL backing, token appreciation, issuer reporting
• Starke — January 2026 validator report · primary · accessed 2026-08-16
  Supports: validator active stake, rkSOL share, delegator distribution, issuer reporting
• DefiLlama — Starke Staked SOL survey record · secondary · accessed 2026-08-16
  Supports: current TVL, Solana, Liquid Staking category, survey observation

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.