Staking Glossary: Validator, Delegation, Slashing, Unbonding, LST, PT and Vault

First, build a “staking map”

Staking is not a single product name, but a collective term for a set of different mechanisms. You might directly hand native tokens to the network’s validator, or obtain transferable certificates through a liquid staking protocol; you might also deposit assets into a Vault managed by a strategy contract. They may all be colloquially called “staking,” but the destination of assets, source of yields, exit methods, and risks are not the same.

Understanding these differences is more important than remembering a yield number. This article explains common terms in order from the underlying layer to the product, and provides a pre-operation checklist. For support scope, product status, or parameters that may change, the query date of this article is 2026-07-31; in actual operations, please refer to the OneKey product page, in-app prompts, and relevant official documentation.

Validator: Validator

A validator is a node that participates in the consensus of a Proof-of-Stake (PoS) network. The network usually requires validators to lock or manage a certain amount of native tokens and undertake responsibilities such as proposing blocks, verifying transactions, and participating in voting. A validator’s online rate, signing behavior, and node configuration affect network security and may also affect delegators’ rewards.

A validator is not a “guaranteed-profit wealth manager.” On different chains, validators may have their own staking thresholds, commissions, active set rankings, maximum delegation amounts, or other rules. Before delegating, confirm:

• Whether the validator is in an active state that can participate in consensus;
• Commission ratio, commission change rules, and historical operational status;
• Whether the network has double-signing, long-term offline, or other behaviors that may lead to penalties;
• When rewards are credited and whether they need to be manually claimed or restaked.

These parameters belong to chain or protocol rules and are not risks that OneKey can eliminate for you.

Delegation: Delegation

Delegation is the allocation of staking rights or related interests in staking assets to a validator to participate in the network. Delegators usually do not need to run their own nodes, but still bear the risks brought by network rules and the chosen validator. The technical meaning of “delegation” is not exactly the same across chains: some chains allow native delegation, some complete it through smart contracts, and others wrap delegation certificates into transferable tokens.

Delegation does not mean permanently transferring asset ownership to the validator. Actual rights depend on the chain’s account model, staking contract, and transaction authorization. Before signing, verify the transaction target, network, asset amount, fees, and whether it includes auto-compounding or other authorizations. Do not only look at the estimated yield on the interface, and do not skip official status pages and commission checks just because the validator name is familiar.

Rewards: Rewards, Commission and Restaking

Staking rewards usually come from protocol issuance, transaction fees, or other network rules. The displayed “yield” may be an estimate and may not deduct validator commission, protocol fees, network fees, price volatility, or tax impact. APR, APY, and “reward rate” are not the same concept: APY usually assumes reward restaking, while actual restaking frequency and cost may differ.

When viewing rewards, break it into four questions: Who pays the reward? By what rules is it calculated? When can it be claimed? Does claiming or restaking incur fees? If the product page provides current data, it may change with network parameters, validator commission, or market conditions. Please refer to OneKey product pages and corresponding official documentation after 2026-07-31.

Slashing: Slashing

Slashing is often translated as “penalty” or “punishment.” It is an economic penalty imposed by the network on validators that commit serious violations, which may include deducting staked amounts, temporarily or permanently removing them from the validator set, and affecting related delegators. Trigger conditions vary by chain; common categories include double signing, equivocation, long-term offline status, or consensus behavior that violates the protocol.

Slashing is different from ordinary reward reductions. Reward reductions usually come from low online rates, commissions, or declining network yields; slashing may directly reduce the staked principal. Delegating to a validator does not mean you will definitely be slashed, but delegators should first read the target chain’s official penalty rules to understand whether validator behavior can be transmitted to the delegator and how the penalty scope is calculated.

Unbonding: Unbonding Period

Unbonding is the waiting phase after initiating an undelegate, cancel delegation, or exit staking request. During the waiting period, assets may not be transferable or re-delegatable, and rewards may also be handled according to chain rules. It is not a wallet failure or a failed transaction, but a state set by the network to maintain security and prevent short-term entry and exit.

The length of the unbonding period is determined by the specific chain and staking implementation and cannot be summarized with a single number of days. The common process is: initiate an undelegate or withdraw request, enter the unbonding state, and wait several cycles before retrieving usable assets. Before submitting, confirm from which block or cycle the countdown starts, whether it can be canceled, whether an additional claim transaction is needed, and whether rewards continue to accrue during the waiting period.

Native Staking: Native Staking

Native staking directly uses the accounts, validators, and exit rules defined by the blockchain itself. Its advantage is a relatively direct path, relying primarily on network consensus and validators; its disadvantage is that liquidity may be limited, exiting requires waiting for the unbonding period, and operational steps vary by chain.

Native staking is not the same as depositing tokens into a DeFi contract. The key risks of the former are network rules, validator operations, and locking or exit arrangements; the latter additionally bears smart contract, oracle, strategy, liquidation, and liquidity risks. Even if the interface says “Stake,” you should still first clarify what contract or module the transaction actually calls.

LST: Liquid Staking Token

LST (Liquid Staking Token) is the abbreviation for liquid staking token. Users hand native assets to a liquid staking protocol, which stakes on behalf of the user and issues a certificate to the user. This certificate can usually be used in other markets or DeFi protocols, so it has greater liquidity compared to direct native staking.

An LST is not the native asset itself, nor is it a risk-free “deposit certificate.” It may trade at a discount or premium to the underlying asset, and exiting may be subject to queue, liquidity, or protocol capacity limits; protocol contracts, validator sets, redemption mechanisms, and smart contract upgrade risks must also be considered. When using an LST as collateral, lending protocol liquidation risk is also layered on top.

When evaluating an LST, check at least three layers: how the underlying asset is staked, how the certificate is priced and redeemed, and whether there is sufficient liquidity in the secondary market. Do not interpret “tradable” as “always redeemable 1:1.”

PT: Principal Token

PT (Principal Token) usually comes from a yield-splitting protocol and represents the principal portion of an asset that can be redeemed on a predetermined maturity date. A common accompanying concept to PT is YT (Yield Token), which represents the right to yields before maturity. The price of a PT usually fluctuates around its maturity redemption value, but is affected by term, interest rates, market liquidity, and protocol risk.

The difference between PT and LST is: LST is primarily a liquid certificate after staking; PT is primarily the principal portion after splitting principal from future yields. Purchasing a PT may mean locking in principal at maturity at a discount, but it does not equal guaranteed returns and may also involve pre-maturity price volatility, early exit losses, contract vulnerabilities, and underlying asset risk. Be sure to confirm the maturity date, redemption asset, yield source, whether a secondary market exists, and whether the product allows early exit.

Vault: Yield Strategy Vault

Vault usually refers to an asset pool or yield strategy container managed by a smart contract. Users deposit an asset and receive share certificates; the Vault then performs staking, lending, liquidity provision, or other operations according to a preset strategy. Yields depend on the actual results of the strategy; fees may include management fees, performance fees, protocol fees, and transaction costs.

“Vault” is not a unified standard. Products with the same name may adopt completely different strategies and permission designs. Before depositing, check which protocols the assets will be deployed to, who can modify the strategy or pause withdrawals, how shares are calculated, and whether withdrawal queues, loss sharing, quota caps, and emergency exit mechanisms exist. If a page only shows a yield without strategy, fee, and risk descriptions, you should not judge product safety based on that.

How to distinguish these terms

You can judge in the following order: first ask whether the asset directly enters the chain’s staking module; if so, focus on validator, delegation, rewards, and unbonding period. If the protocol issues transferable staking certificates, focus on LST redemption and liquidity. If assets and future yields are split with a maturity date, focus on PT, YT, and term. If assets enter a pool managed by a strategy contract, focus on the Vault’s strategy, permissions, and exit mechanism.

When verifying related features in OneKey, only use the assets, networks, actions, and statuses actually returned by the current product or API. Interface fields may contain staking, validator, delegation, reward, unbonding, or other product terms, but “API field present” does not equal support for all chains, all validators, or all strategies. Do not infer from similar names that a certain Vault, Provider, address, or DeFi product is supported by OneKey; if the product page or official documentation does not explicitly list it, treat it as pending confirmation.

Pre-operation checklist

• Confirm network and asset: check chain name, token contract (if applicable), balance, and fee asset.
• Confirm mechanism: distinguish between native staking, delegation, LST, PT, and Vault; understand the contract or chain module the transaction will call.
• Confirm exit: record unbonding period, maturity date, redemption conditions, withdrawal queue, and possible additional transactions.
• Confirm fees: check validator commission, protocol fees, exchange fees, Gas, and slippage; do not treat gross yield as net yield.
• Confirm permissions: review smart contract authorizations, strategy administrators, pause permissions, and upgrade permissions.
• Confirm risk: understand whether slashing affects delegators, whether LST may depeg, whether PT has term loss, and whether Vault may incur losses.
• Small-amount trial: for first-time operations, use a small amount of assets you can afford to lose; save the transaction hash and observe whether the status matches expectations.

Risk Disclosure

Staking, liquid staking, yield splitting, and Vaults may all result in loss of principal. Risks include but are not limited to token price volatility, validator slashing or offline status, inability to use assets during the unbonding period, smart contract vulnerabilities, administrator or upgrade permissions, oracle failures, insufficient liquidity, depegging, liquidation, slippage, and network congestion. Any expected yield is not a promise and does not constitute investment, tax, or legal advice. OneKey’s interface or API display does not change the risk-bearing relationship of underlying chains and third-party protocols. Support scope, fields, rates, and product status will change; the query date for information in this article is 2026-07-31. Please refer to OneKey product pages, actual in-app prompts, and relevant official documentation.

References

• Ethereum Official: Staking Introduction
• Cosmos Hub Official Documentation: Delegation and Unbonding
• Polkadot Wiki: Staking and Slashing
• Lido Official Documentation: stETH and Liquid Staking
• Pendle Official Documentation: PT and YT
• Yearn Official Documentation: Vault Overview