Companies and projects covered
Prepared by the Token Metrics Editorial Team using the official sources listed below. Product terms, eligibility, limits, fees, and protocol rules can change; confirm current details before acting.
Safety note: Staking can expose a user to market loss, lockups or exit delay, validator penalties, smart-contract risk, counterparty risk, and tax questions. Yield is not guaranteed. Confirm current rules and use a small test before you commit assets.
Quick verdict: Solo staking fits a skilled operator who wants direct validator control. Lido fits a user who wants a liquid-staking token and accepts added protocol and token risk. Rocket Pool offers a pooled route plus a separate node path. A custodial service can be easier but adds account and provider risk. Choose the custody path first, not the highest shown rate.
Comparison matrix
| Path | Key or account control | Work required | Liquidity and exit | Main added risk |
|---|---|---|---|---|
| Solo staking | Operator controls validator and withdrawal setup | High | Protocol exit process; no liquid token by default | Operations, keys, downtime, penalties |
| Lido | User wallet plus protocol contracts | Low to medium | Liquid token and documented exit paths | Contracts, operators, governance, token market |
| Rocket Pool pooled | User wallet plus protocol contracts | Low to medium | Protocol token and documented exit path | Contracts, operators, governance, token market |
| Rocket Pool node | Node operator manages node duties | High | Node and protocol exit rules | Operations plus protocol and collateral duties |
| Custodial service | Provider controls the account-side staking flow | Low | Provider withdrawal rules | Custody, account, counterparty, eligibility |
Criterion-by-criterion analysis
Control
Solo staking gives the operator the most direct work and control. Protocol routes keep wallet control at entry but add contracts. Custodial routes give the provider more control.
Technical burden
Solo and node operation need hardware, client, update, monitoring, and recovery skills. Pooled and custodial routes reduce that work but do not remove risk.
Liquidity
A liquid token may be usable before a full protocol exit, but its market value can move. A provider can set its own withdrawal steps. Solo exit follows network rules.
Risk layers
Count every layer: wallet, contract, operator, governance, token, other app, platform, and bank. A simple screen can hide a long risk chain.
Costs and records
Compare protocol or service fees, gas, token trades, hardware, and support work. Make sure the path gives records for deposits, rewards, fees, token events, and exits.
Who each option fits
- Solo: a technical operator who can maintain the validator and key process.
- Lido: a self-custody user who understands liquid-token and protocol risk.
- Rocket Pool pooled: a user comparing a different pooled protocol design.
- Rocket Pool node: an operator ready for node and protocol duties.
- Custodial service: a user who accepts provider custody and wants a simpler account flow.
Scenarios
Long-term holder with no server skill
A node path is a poor fit if the user cannot maintain it. The user can compare pooled and custodial paths, or choose not to stake. The best next step is to map custody and exit, not chase a live rate.
Technical user who wants direct control
Solo staking may fit if the user can run clients, protect keys, monitor uptime, update software, and handle recovery. A node protocol can add pool duties and should be reviewed on its own.
User who needs near-term liquidity
A liquid token can offer market liquidity, but the token can move away from the expected value and adds contract paths. A planned cash need may make no staking the safer fit.
Decision checklist
- Choose the custody model.
- List the skill and time needed.
- Read entry, fee, penalty, reward, and exit rules.
- Count contracts, operators, tokens, and platforms.
- Check liquid-token market and app risk.
- Confirm records and local advice needs.
- Test with a small amount and a known exit.
Frequently asked questions
Which option is best for beginners?
There is no automatic beginner winner. A simpler screen can still add custody or contract risk. A beginner can also choose not to stake.
Are Lido and Rocket Pool the same?
No. Both are protocol routes, but their designs, tokens, operator systems, and user paths differ. Read each current guide.
Is solo staking risk free?
No. It removes some provider layers but adds direct key, validator, hardware, software, uptime, and penalty duties.
Should I compare yield first?
No. Compare custody, exit, risk layers, skill, and records first. Rates change.
Run a withdrawal-control drill before choosing
Use a small, reversible test before committing meaningful funds. Write down who holds the keys, who selects the validator, which contract or provider controls withdrawal, the expected unbonding path, every disclosed fee, and the support route if the interface fails. Then complete the smallest permitted stake and withdrawal while saving transaction identifiers and current documentation. A successful drill does not eliminate protocol, slashing, smart-contract, or counterparty risk, but it reveals whether the real workflow matches the comparison table. Reject an option when custody language is vague, withdrawal steps cannot be reproduced, or the net reward cannot be reconciled after fees. For pooled or liquid staking, also test how the receipt token is redeemed and what happens if its market price diverges from the underlying asset.
Sources
These primary and public-interest sources were checked on July 13, 2026. Product terms can change, so confirm the current page before you build or move assets.
- Ethereum staking overview
- Ethereum solo staking
- Ethereum pooled staking
- Lido docs
- Rocket Pool docs
- FTC crypto scam guidance
- IRS digital assets
Disclosure: Token Metrics may earn compensation from some partner links. Compensation does not decide coverage or conclusions. This page is for education. It is not investment, legal, tax, custody, compliance, or engineering advice.
Continue: staking workflow guide · methodology · comparison · custody-fit checker
Practical review notes
Common ground
All staking paths begin with a choice to put assets at risk for a possible reward. None can remove market risk. Each path also needs good account or wallet care, clear records, and a known exit. The key split is who holds the keys and who runs the work.
Key difference
Solo and node paths move more work to the user. Pool paths move some work to code and operators. A service path moves more work and control to a firm. The screen may look easy in each case. The risk map is not the same.
Before a final choice
Read the current start and exit guide on the same day. Check the domain on your own. Save the fee and risk page. Use a small amount. Confirm the record. Then test how an exit starts. Do not add another app or token until the first path is clear.
A fair comparison rule
Use the same amount, time need, custody need, and skill level for each path. Do not compare one live rate with an old rate from another page. Do not call a token liquid without checking the market and exit. State what is known, what may change, and what was not tested.
Write down the choice
Save the path, date, source pages, and open risks. Note why the other paths did not fit. This makes a later review fair. It also helps a user spot when a new fee, rule, or need should change the choice.
