Skip to main content
Native staking lets you stake SOL directly with the Jupiter validator through a . Your SOL remains in a stake account you own; it is not transferred to Jupiter. The Jupiter validator takes a 5% commission on inflation rewards and 0% on rewards. All actions are non-custodial and executed directly from your wallet.

​
How to Stake

Follow these steps to stake SOL natively with the Jupiter validator.
1

Enter the amount of SOL to stake

On the Native tab of the Jupiter Stake page, enter the amount of SOL you want to stake. The minimum is Solana’s minimum delegation, currently 1 SOL; the form shows it (Minimum stake is … SOL) and blocks smaller amounts. A small extra amount of SOL, shown in the form, stays unstaked in the stake account as its rent reserve.
2

Delegate to the Jupiter validator

Click Delegate. This creates a native stake account and delegates your SOL to the Jupiter validator.
3

Wait for activation

Your stake activates at the start of the next Solana . Epochs currently last about a day, so the wait depends on when in the current epoch you stake: the form shows the time until the next payout.
4

Earn rewards

Once active, your stake earns rewards every epoch. Both inflation rewards and MEV rewards are auto-compounded into your stake account.

​
Rewards

Staking with Jupiter Stake earns two types of rewards. Both are auto-compounded into your stake account every epoch. No manual claiming is needed. The validator takes a 5% commission on inflation rewards and 0% on MEV.
Standard Solana staking rewards, paid by the network to validators and their delegators at the end of each epoch. These rewards come from Solana’s inflation schedule. The Jupiter validator takes a 5% commission on them.
Additional revenue from Maximal Extractable Value (MEV). MEV refers to the extra value a validator can capture by optimizing the ordering of transactions within a block. Jupiter redistributes 100% of MEV rewards to stakers.
Staking rewards are variable. The estimated APY displayed on the interface depends on network conditions, validator performance, and MEV activity. It is not fixed and not guaranteed.

​
Unstaking and Unlock Period

Unstaking follows Solana’s epoch schedule, not a fixed timer.
1

Initiate unstaking

Your stake begins deactivating.
2

Wait for the epoch to end

Deactivation completes at the end of the current epoch (up to about a day, depending on when you unstake). During the unlock period, your SOL does not earn rewards.
3

Withdraw your SOL

Once fully deactivated, you can withdraw your SOL from the Manage page.

​
Managing Your Stake

The Manage page gives you an overview of your staking position. Open it from Manage in the summary under the Stake form, once your wallet is connected.

​
Stake Account Actions

Each stake account shows the actions available for its current state:
  • Deactivate: begins deactivation, following the epoch schedule described above.
  • Delegate: re-delegates a deactivating or inactive stake account to the Jupiter validator without withdrawing.
  • Withdraw: reclaims SOL from a fully deactivated account.
  • Split: divides one stake account into two. Both resulting accounts must keep at least the minimum delegation, and the rent for the new account is paid from your wallet.
  • Merge: combines compatible stake accounts into one, up to 20 source accounts per transaction. Each merged account is closed and its full balance, including rent, is added to the remaining account. Accounts must share the same authorities and be either fully active on the same validator or both inactive.
  • Switch to JupSOL: converts a stake account, in whole or in part, into JupSOL without waiting for deactivation. Converting a whole account also deposits its rent reserve.
The account list refreshes after every action. Around epoch boundaries, an action can temporarily fail while staking rewards are being distributed, or because the JupSOL pool has not been updated for the new epoch yet; this resolves within a few minutes.
Stake accounts delegated to other validators also appear in the list, but the only action available for them is deactivation. Merging requires the accounts to be compatible with each other, and converting to JupSOL requires the stake account to be delegated to a validator in the JupSOL pool. These are Solana-level constraints, not restrictions added by Jupiter.

​
Risks and Limitations

The following risks apply specifically to native staking with Jupiter Stake.
Staking APY fluctuates based on network conditions, validator uptime, and MEV activity. Past performance does not predict future returns.
Both activation and deactivation follow the Solana epoch schedule (an epoch currently lasts about a day). You cannot access your SOL during the unlock period.
If the Jupiter validator experiences downtime or poor performance, your rewards for that period may be reduced. Slashing risk on Solana is currently negligible, but the protocol allows for it.
You unstake whole stake accounts. To unstake part of a position, split the stake account first, then deactivate one of the resulting accounts (each must keep at least the minimum delegation, currently 1 SOL).
Solana no longer supports redelegating a stake account from one validator to another; the feature existed in the past and was disabled for security reasons. To move a stake delegated to another validator over to Jupiter, unstake it, wait for deactivation to complete at the end of the epoch, then stake again. The same applies in the other direction.

​
Native Staked Vaults

Your natively staked SOL doesn’t have to sit idle. Native Staked Vaults on Jupiter Lend let you borrow SOL against your staked position, without unstaking and without interrupting your staking rewards.
This section covers the Native Staked Vaults functionality as it relates to Jupiter Stake. For the full Jupiter Lend documentation on Native Staked Vaults, see Jupiter Lend: Native Staked Vaults.

​
How It Works

The following steps describe how to use your natively staked SOL as collateral on Jupiter Lend.
1

Stake SOL with Jupiter Stake

Stake your SOL with Jupiter Stake (or another supported validator). This creates a native stake account delegated to that validator.
2

Deposit your stake in the nsJUPITER / SOL vault

Once the stake is active, open the nsJUPITER / SOL vault on Jupiter Lend: it lists your active stake accounts delegated to Jupiter. The deposit converts the stake you select (or the part you enter) into nsJUPITER, a yield-bearing token minted by the , and supplies it as collateral in the same transaction. nsJUPITER does not sit in your wallet as a regular token.
3

Borrow SOL on Jupiter Lend

Borrow SOL against your nsJUPITER collateral. Your staking rewards continue to accrue while your position is used as collateral.

​
nsJUPITER: Yield-Bearing Representation

When you deposit stake delegated to Jupiter Stake into Jupiter Lend, it becomes nsJUPITER collateral. This token is minted by the Single Pool Program, an open-source program of the Solana Program Library, in exchange for active stake delegated to its validator. Withdrawing collateral gives you back a stake account delegated to Jupiter, not liquid SOL.
The amount of nsJUPITER you hold stays the same over time. Its value increases as staking rewards accrue on the underlying stake account. This also means you can borrow more SOL over time as your collateral value grows.
The naming convention for all Native Staked Vaults is ns + validator name. For Jupiter Stake, it’s nsJUPITER. Other supported validators follow the same pattern (e.g., nsHELIUS, nsDAWN).

​
Validator-Specific Vaults

Each Native Staked Vault is linked to a specific validator. Staked SOL from one validator can only be used in its corresponding vault. Jupiter Lend supports several validators. The Jupiter Stake vault (nsJUPITER / SOL) is the primary one covered in this documentation. For the full list of supported validators, see Supported Validators.

​
Contract-Based Pricing

Native Staked Vaults use contract-based pricing, not market-based pricing.

​
Borrowing

Once your stake is deposited in the nsJUPITER / SOL vault, you can borrow SOL against it. All borrowing actions are signed from your wallet and executed on-chain. Your deposited stake joins Jupiter’s single-validator stake pool, shared by all its depositors, and the resulting nsJUPITER is held as collateral by the Jupiter Lend smart contracts.
Native Staked Vaults support borrowing SOL only. Multiply is not available for these vaults.

​
Risks Specific to Native Staked Vaults

These risks apply in addition to the general native staking risks listed above.
If the value of your collateral falls relative to your borrowed amount, your position may be liquidated. Monitor your health ratio regularly.
Crypto market volatility can affect the value of your collateral and your borrowing position, even with contract-based pricing.
Collateral and debt are both priced in SOL. If the SOL borrow rate exceeds your staking yield, your debt grows faster than your collateral and your ratio rises over time, even without any price move.
Staked SOL from one validator can only be used in that validator’s vault.

​
Security and Audits

Native Staked Vaults rely on two standard Solana programs, both audited and widely used, and on the Jupiter Lend programs (vaults, liquidity layer, oracle), which carry their own smart contract risk. Their audits are listed on the Security page.
The native Solana program used to create and manage stake accounts. Part of Solana’s core infrastructure, audited and battle-tested across the network.
Handles the conversion from a native stake account to its yield-bearing representation (nsTOKEN). An open-source program of the Solana Program Library (solana-program/single-pool). Shared across all supported validators and not specific to Jupiter.Audited three times:Audit reports on GitHub
Jupiter Lend integrates these audited programs to allow native stake positions to be used as collateral. All staking, minting, and borrowing actions are signed from your wallet and executed on-chain.