How to use liquid staking tokens in Phantom? (LST guide)

Liquid Staking Token Integration in Phantom Wallet

1. Phantom wallet natively supports mSOL and jSOL as recognized assets once connected to Solana mainnet. No manual token addition is required for major LSTs issued by Marinade Finance or Jito.

2. Upon completing a staking action via Marinade or Jito interface while connected to Phantom, the wallet automatically detects and displays the corresponding LST balance under the “Assets” tab.

3. Phantom displays real-time LST balances alongside native SOL, with on-chain balance verification performed directly through Solana RPC endpoints.

4. Users can initiate transfers of mSOL or jSOL directly from the asset list by selecting the token, entering recipient address, and confirming transaction signature.

5. Phantom does not support direct LST redemption within its UI; users must navigate to the issuing protocol’s interface to unstake and convert back to SOL.

Transferring and Swapping LSTs via Phantom

1. Clicking an LST in Phantom’s asset list opens a context menu with “Send”, “Swap”, and “View on Explorer” options.

2. The built-in swap function routes orders through Jupiter Aggregator, enabling seamless exchange between mSOL/jSOL and tokens like USDC, RAY, or BONK.

3. Slippage tolerance and route optimization are handled automatically, with estimated output and network fee shown before confirmation.

4. All swaps execute as atomic Solana transactions—no intermediate approvals or bridging steps are needed for same-chain LST conversions.

5. Transaction history reflects both the swap instruction and the underlying LST transfer event, preserving full auditability on-chain.

Using LSTs in DeFi Protocols Through Phantom

1. Phantom enables one-click connection to Raydium, Orca, and Saber by detecting wallet compatibility and injecting necessary signing capabilities.

2. When adding mSOL to a liquidity pool, Phantom signs only the token approval and LP mint instructions—not the underlying SOL delegation logic.

3. Depositing jSOL into Solend triggers automatic interest accrual tracking; Phantom displays accrued yield in real time based on on-chain oracle feeds.

4. Collateralized borrowing using LSTs follows standard Solend risk parameters: mSOL maintains 75% LTV, while jSOL carries 70% LTV due to validator diversification differences.

5. Phantom surfaces health factor warnings when borrowed positions approach liquidation thresholds, pulling data directly from Solend’s on-chain state.

Security Considerations for LST Management

1. Phantom never stores private keys or executes smart contract logic—every LST-related action requires explicit user signature via hardware or software wallet flow.

2. Validator uptime and commission rates for underlying SOL delegation are not visible inside Phantom; users must verify these metrics externally via StakeWiz or Solana Compass.

3. Phantom displays LST contract addresses and token decimals in asset detail view, allowing manual verification against official Marinade or Jito deployments.

4. Phishing detection blocks access to known counterfeit LST token lists, preventing accidental interaction with fake mSOL or jSOL contracts.

5. Phantom disables auto-refresh during active LST transactions to prevent race conditions that could lead to duplicate submissions or incorrect balance displays.

Frequently Asked Questions

Q1: Does Phantom support staking SOL directly into liquid staking protocols?Yes. Phantom allows direct navigation to Marinade Finance and Jito websites with pre-authorized wallet connection, enabling single-signature staking initiation without switching tabs manually.

Q2: Can I see my underlying SOL delegation status inside Phantom?No. Phantom shows only LST balances and transaction history. Delegation details—including assigned validators, epoch rewards, and uptime statistics—must be retrieved from protocol dashboards or Solana explorers.

Q3: Are mSOL and jSOL balances updated instantly after protocol rebasing?Yes. Phantom fetches token balances on every wallet load and refreshes them via SPL token program account data reads, reflecting rebased supply changes within seconds of on-chain settlement.

Q4: What happens if I send mSOL to a non-Solana chain via Phantom?Phantom prevents cross-chain transfers of LSTs by disabling bridge integrations for unsupported tokens. Attempting to select a non-native chain triggers an error warning and halts the transaction flow.