How Does Jupiter Staked SOL Work?
Jupiter Staked SOL (jupSOL) is Jupiter Exchange's liquid staking token on Solana, built in partnership with Sanctum. When you stake SOL through Jupiter, you receive jupSOL which earns staking rewards while remaining usable across DeFi. jupSOL is unique in that it uses Jupiter's own validator running the experimental Frankendancer client, and 50% of staking revenue goes to buying JUP tokens.
TVL
$826M
Sector
Liquid Staking
Risk Grade
B
Value Grade
B-
Core Mechanisms
Staking/Liquid-Staking
jupSOL: liquid staking token for SOL with exchange-rate appreciation model reflecting accrued staking rewards
Users deposit SOL and receive jupSOL at an exchange rate. jupSOL appreciates over time as staking rewards accrue. Built in collaboration with Sanctum's infrastructure.
Staking/Validator-Client
NovelJupiter validator running Frankendancer experimental Solana client in Frankfurt and Madrid data centers
Frankendancer is a next-gen Solana validator client under active development. Running on an experimental client provides performance benefits but introduces software risk from untested codepaths.
Value-Capture/Buyback
50% of jupSOL staking revenue directed to JUP token buybacks starting February 2025
Revenue split between staker yield and JUP buybacks. This means jupSOL yield is structurally lower than competing LSTs that pass 100% of rewards to holders.
Integration/Sanctum
Built on Sanctum's validator LST infrastructure for liquidity and swaps
jupSOL leverages Sanctum's unified liquidity layer for instant unstaking and LST-to-LST swaps. Creates dependency on Sanctum's infrastructure for liquidity.
Integration/Super-App
Deep integration with Jupiter's DEX, perps, lending, and stablecoin ecosystem
jupSOL can be used as collateral across Jupiter's lending and perps products. Integration drives utility but ties jupSOL's value proposition to Jupiter's overall ecosystem health.
How the Pieces Interact
Running an experimental validator client creates risk of bugs, consensus failures, or performance issues that could cause slashing or downtime, directly reducing jupSOL holders' returns.
Diverting half of staking revenue to buybacks makes jupSOL structurally less competitive on yield versus JitoSOL, mSOL, and other Solana LSTs. If JUP price declines, the buyback subsidy provides no benefit to jupSOL holders.
jupSOL's instant unstaking and swap liquidity depend on Sanctum's router and reserve pool. A Sanctum outage or smart contract issue would strand jupSOL holders without a liquidity exit path.
jupSOL used as collateral in Jupiter Lend or perps creates cross-product exposure. A depeg or smart contract issue in jupSOL cascades through positions across the Jupiter ecosystem.
What Could Go Wrong
- jupSOL is delegated primarily to Jupiter's own validator running the experimental Frankendancer client, creating concentration and software risk
- 50% of staking revenue is used to buy back JUP tokens, meaning jupSOL holders subsidize token buybacks with reduced yield
- Deep integration in Jupiter's super-app ecosystem creates dependency — jupSOL's utility is tied to the health of the broader Jupiter platform
Frankendancer Client Failure Causes Slashing
TailTrigger: A critical bug in the Frankendancer experimental validator client causes Jupiter's validator to produce invalid blocks or double-sign, triggering Solana slashing penalties
- 1.Frankendancer client bug causes Jupiter's validator to produce conflicting blocks — Solana consensus triggers slashing penalty against Jupiter's validator
- 2.Slashing reduces the SOL backing of jupSOL tokens — jupSOL exchange rate drops below expected value; holders face immediate loss
- 3.jupSOL holders rush to redeem or swap via Sanctum — Sanctum reserve pool depleted; jupSOL depegs on secondary markets
- 4.Positions using jupSOL as collateral in Jupiter Lend are liquidated — Cascading liquidations across Jupiter's lending platform
Risk Profile at a Glance
Overall: B (25/100)
Lower score = safer