How it works
The process follows three steps:- Stake native SOL with a supported validator.
- A representation of your staked position (nsTOKEN) becomes visible within Jupiter Lend.
- Use it as collateral to borrow SOL on Jupiter Lend.
Yield-bearing token representation (nsTOKEN)
Yield-bearing token representation (nsTOKEN)
On Jupiter Lend, native stake accounts are represented by yield-bearing tokens called nsTOKENs. The naming convention is ns + validator name (e.g., nsJUPITER for SOL staked with Jupiter Stake, nsHELIUS for Helius).This token is not displayed as a regular asset in your wallet. 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
Validator-Specific Vaults
Each native staking vault is 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 configurations in the future.
How Staking Earnings Are Managed
How Staking Earnings Are 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. The amount of nsTOKEN remains the same; only its value increases. There is no manual claiming or reinvestment required.This means:
- Your nsTOKEN value increases over time as staking rewards are added.
- The increased value can be used to borrow more SOL on Jupiter Lend.
Limitations
Limitations
- Only SOL can be borrowed from Native Staked Vaults.
- Each vault supports one collateral pair tied to one validator.
- Available only in Borrow (not in Multiply).
- Staking and unstaking periods are specific to each validator.
Supported Validators
Jupiter Lend supports multiple Native Staked Vaults, each linked to a specific Solana validator. All follow the same borrowing mechanics and user flow.- Jupiter Stake — nsJUPITER / SOL
- Helius — nsHELIUS / SOL
- Nansen — nsNANSEN / SOL
- Blueshift — nsSHIFT / SOL
- Kiln — nsKILN / SOL
- Temporal — nsTEMPORAL / SOL
Contract-Based Pricing
Native Staked Vaults use contract-based pricing rather than market-based pricing. This means the collateral value is derived directly from the underlying stake account, and liquidation logic is based on the true staked value rather than market price.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
Native Staking as Collateral relies on two standard Solana programs, both audited and widely used.Stake Program (Validator Staking)
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.
Single Pool Program (Stake Account to nsTOKEN conversion)
Single Pool Program (Stake Account to nsTOKEN conversion)
The conversion from a native Solana stake account to its yield-bearing representation (nsTOKEN) is handled by the Single Pool 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:
- Zellic (2023-06-21)
- Neodyme (2023-08-08)
- Zellic (2024-01-02)

