Native staking, managed staking and liquid staking compared

Self-managed staking gives you a named stake position

With native staking, you hold SOL in a stake account and choose its validator vote address. The account records its authorities, delegation and relevant state. You can inspect it directly and use supported instructions to manage it.

The standard exit requests deactivation, waits for the appropriate account state and withdraws the eligible amount. There is no transferable LST merely because SOL is delegated.

This arrangement suits someone who wants to choose an operator and follow a specific position. It also means you make the selection and management decisions. A wallet simplifies the instructions but does not eliminate the underlying account lifecycle.

Read native staking from start to finish for the operational sequence. Here the comparison focuses on how other products change that structure.

Managed native staking separates management from withdrawal

A managed native product can automate validator allocation while using native stake accounts. The central question is which authority you assign and which you retain.

Marinade Native's current documentation describes the user retaining withdrawal authority while its management mechanism controls stake authority. It also identifies a Native Staking Proxy program and PDAs in the management path. This is an authority split supported by programs, not an absence of program dependencies.

The user does not receive mSOL simply by using that native arrangement. The service can manage delegation through the permitted stake role, while the stake accounts remain the positions to inspect.

Check how the product handles account splitting, rebalancing and rewards for smaller positions. An automated strategy can have operational effects that differ from keeping one unchanged delegation.

A liquid staking token represents a pool position

A liquid staking pool accepts eligible assets and issues a token representing participation in its assets under the pool's rules. Examples include mSOL and JitoSOL. The pool manages backing stake and validator selection through its program and operating mechanism.

The token holder controls the LST according to its token rules. That is different from personally holding the withdrawal authority for each underlying stake account. The pool's program connects tokens with the backing and supported exits.

For an exchange-rate-style LST, rewards can appear as more underlying value per token rather than an increase in the number of tokens in your wallet. Different products define their own accounting and charges.

Use a teaching ratio of 1.10 SOL per LST. Ignoring charges, depositing 11 SOL would correspond to 10 LST under that chosen ratio. This explains units; it is not a quoted mSOL or JitoSOL exchange rate. A later market sale can use another price.

Token units and underlying conversion differ

Compare deactivation, redemption and market sale

A native deactivation follows stake-account state. A pool redemption follows the pool's supported process, available assets and charges. A market sale exchanges the LST for a quoted amount through available trading liquidity.

At the teaching ratio, 10 LST can correspond to a pool value of 11 SOL, while a market quote might offer a different amount. Fees, depth and conditions determine the actual result. A token being transferable does not guarantee a sale at its accounting value.

Some managed-native products also provide a quoted exit from native stake. Marinade's documentation describes a market-maker quote for its instant route and a distinct delayed route. The latter can involve a service charge and a separate claim transaction. Read the exact current route you select.

A useful comparison names the input position, amount received, waiting or eligibility condition and each expense. The word unstake alone does not describe all these mechanisms.

Read income and charges under one method

Native staking can expose epoch rewards and validator commission. A managed product adds its selection policy and any product charges. A pool can reflect staking and other supported rewards through its conversion accounting.

Use a ready-made yield observation from a documented provider or the product's own defined method, keeping the period and update time visible. Do not subtract a fee twice if the published figure already includes it.

For validator comparisons, SolanaBull's data policy is to use a verified delegator-yield API, with providers kept separately labelled. Operator-plus-delegator income is not silently substituted for the delegator's return.

Income in SOL and performance in a national currency are separate measurements. When an LST is used in another protocol, that creates an additional position with another income and loss mechanism. It should not be described as a free extension of native staking.

Match the holding to the task you need

If you want to choose a particular validator, inspect the direct stake-account route. If you want delegated management while retaining a withdrawal role, inspect the managed product's exact authority arrangement. If you need a transferable position token, inspect an LST's program and exits.

Then follow the complete lifecycle with the intended amount. Determine what you hold after entry, how you observe income, who can manage it and how the assets become available at exit.

Keep the final comparison compact: holding, controlling roles, validator selection, reward accounting, costs, exit route and data source. Those fields let the reader choose on a clear mechanical basis instead of a large percentage in a banner.

Compare the same intended use across the three models

Consider a reader who wants exposure to staked SOL but also wants to name two validators. With self-managed native staking, the reader can maintain separate stake accounts delegated to those vote accounts, retaining the relevant authorities. The accounts' activation and deactivation states determine the available next actions.

A managed native route can select and change validators under its management authority. The question becomes whether the product supports the reader's requested allocation, rather than whether the wallet displays a staking tab. Retaining withdrawal authority and delegating management are different control decisions.

An LST holder owns the receipt token, while the pool selects its backing validators. Splitting the token between two wallet accounts does not create two independently selected validator delegations. An application can accept the receipt as collateral, but that adds a lending position and its exit requirements.

Now change the reader's goal to spending SOL on a particular date. Compare native deactivation, the managed product's supported exit and the LST's redemption or market sale. A transferable token can have an available sale at a discount, while an accounting claim may require time before SOL becomes spendable. Use the LST exit comparison to calculate those routes on the same holding.

The model that fits follows from the required control and exit. A single annualized percentage cannot answer whether a particular validator can be selected, a position can enter DeFi or the output will be available on the intended date.

Common questions