Native staking secures the Solana network and rewards users, but it traditionally comes with a trade-off, staked SOL is locked and cannot be used elsewhere.
Jupiter removes this trade-off by allowing users to borrow against their natively staked SOL, without unstaking and without interrupting rewards.
Native Staking Vaults on Juplend allows users to use their staked position directly as collateral on Jupiter Lend.
How it works?
This process follows three simple steps:
- Stake Native SOL
- A representation of the staked token is visible within Jupiter Lend
- Use it as collateral to Borrow on Jupiter Lend
Yield-bearing token representation (nsTOKEN)
On Jupiter Lend, native stake accounts are represented by yield-bearing tokens called nsTOKEN, used to represent natively staked SOL as collateral.
This token is not displayed as a regular asset in your wallet. Instead, it exists on-chain and is surfaced directly within Jupiter Lend, where it can be used as collateral.
Each nsTOKEN represents your share of a native Solana stake account and continuously accrues staking rewards.
Example: If you stake SOL using Jupiter’s validator (Jupiter Stake), your stake account is represented by nsJUPITER.
Validator-specific vaults
Each native staking vault is currently linked to a specific validator.
This means staked SOL from one validator can only be used in its corresponding vault. Jupiter Lend may support additional vault setups in the future.
How stake earnings is managed
Staking rewards earned on native staked SOL are automatically compounded.
As rewards accrue, the value represented by your nsTOKEN increases over time to reflect the additional SOL earned from staking.
The amount of nsTOKEN remains the same, only its value increases. There is no manual claiming or reinvestment required, compounding happens in the background.
This means:
- Your nsTOKEN value increase over time as staking rewards are added
- The increased value can be used to Borrow more SOL on Jupiter Lend
Example: If after 6 months your staked SOL has earned $100 worth of staking rewards, the value represented by your nsTOKEN increases by $100. You can then borrow more SOL against it.
Limitations & current scope
- Borrow only in SOL
- One pair = one validator
- Available only in Borrow (not in Multiply)
- Staking & Unstaking period: Specific to each validator
Active supported Validators on Juplend
Jupiter Lend supports multiple Native Staking Vaults, each linked to a specific Solana validator.
All native staking vaults follow the same borrowing mechanics and user flow.
Supported Validators:
- Jupiter Stake → nsJUPITER / SOL
- Helius → nsHELIUS / SOL
- Nansen → nsNANSEN / SOL
- Blueshift → nsSHIFT / SOL
- Kiln → nsKILN / SOL
- Temporal → nsTEMPORAL
Each validator has its own native staking vault and stake representation token, but the borrowing logic and user experience remain the same.
Additional native staking vaults will be added progressively.
Step-by-Step
The process is identical across all supported validators:
- Stake SOL natively with a supported validator
- Wait for stake activation (epoch-based, ~2–3 days)
- A yield-bearing native stake representation is created on-chain
- Go to Jupiter Lend → Borrow → Native Staked Vaults
- Deposit the native stake token as collateral
- Borrow SOL against it
This flow is fully on-chain, non-custodial, and does not require liquid staking tokens.
Oracle and risks
Contract-based pricing
Native staked Vaults uses contract-based pricing rather than market-based pricing.
This means:
• The collateral value is derived directly from the underlying stake account
• Liquidation logic is based on the true staked value
Market Risk
Crypto market volatility can affect the value of your collateral and your borrowing position. Monitor your position regularly.
All staking and borrowing actions are executed on-chain, directly from the user’s wallet, without custody or asset pooling by Jupiter.
Security and audits
Programs used for native staking collateral
Native Staking as Collateral relies on two standard Solana programs, both audited and widely used.
1. Stake Program (validator staking)
This is the native Solana program used by all supported validators to create and manage stake accounts.
It is part of Solana’s core infrastructure, audited, and battle-tested across the network.
2. Single Pool Program (Stake account → nsTOKEN conversion)
The conversion from a native Solana stake account to its yield-bearing representation (nsTOKEN) is handled by the Single Pool Program, a program deployed and maintained by the Solana Foundation.
This program is shared across all supported validators and is not specific to Jupiter.
It has been audited three times by security firms:
- Zellic (2023-06-21)
- Neodyme (2023-08-08)
- Zellic (2024-01-02)
https://github.com/solana-program/single-pool/tree/main?tab=readme-ov-file#security-audits
Jupiter Lend integration
Jupiter Lend integrates this audited program to allow native stake positions to be used as collateral.
All staking, minting, and borrowing actions are executed on-chain, directly from the user’s wallet, without custody or pooled asset management by Jupiter.