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.
Scope: This method reviews Ethereum solo, service, pooled, liquid, and custodial staking workflows. It asks how a user enters, holds, earns, records, and exits. It does not predict yield, rate a token, or certify a platform.
Evidence hierarchy
- Ethereum protocol and staking documentation for network rules.
- Official protocol or provider docs for the exact workflow.
- Official contracts, audits, terms, fee, and risk pages where available.
- Regulator and consumer guidance for public risk context.
- Hands-on tests for user steps and tool behavior. Marketing is not enough for a material claim.
Non-scoring policy
We do not use an overall score. A number can make unlike paths look alike. Solo staking may offer control but needs more work. Liquid staking may offer a usable token but adds contracts and market risk. A custodial platform may be easy but adds counterparty and account risk. We state the tradeoff instead of hiding it in a weight.
Custody and keys
Who can sign, withdraw, recover, or block access? We seek direct proof in current docs. If the answer is unclear, the page states that limit and tells the reader what to confirm.
Protocol and contracts
Which code, oracle, governance, or upgrade paths affect funds? We seek direct proof in current docs. If the answer is unclear, the page states that limit and tells the reader what to confirm.
Validator operations
Who runs clients, maintains uptime, updates software, and handles penalties? We seek direct proof in current docs. If the answer is unclear, the page states that limit and tells the reader what to confirm.
Exit and liquidity
How does a user request an exit, and what can delay or change value? We seek direct proof in current docs. If the answer is unclear, the page states that limit and tells the reader what to confirm.
Fees and rewards
How are fees taken, how are rewards shown, and which values can change? We seek direct proof in current docs. If the answer is unclear, the page states that limit and tells the reader what to confirm.
Eligibility and support
Which users and places can use the flow, and who handles a failed step? We seek direct proof in current docs. If the answer is unclear, the page states that limit and tells the reader what to confirm.
Records and tax support
Can the user export a clear record of deposits, rewards, token events, fees, and withdrawals? We seek direct proof in current docs. If the answer is unclear, the page states that limit and tells the reader what to confirm.
Research process
- Define the user path and page role.
- Draw the custody and signing path from wallet to exit.
- List every material claim and map it to a primary source.
- Separate protocol facts from vendor statements and our analysis.
- Test the user flow or checker where possible at desktop and mobile sizes.
- Edit to plain language and add risk, disclosure, sources, internal links, and a clear next step.
Freshness policy
Every article shows when its sources were checked. We recheck after a major protocol, contract, fee, eligibility, custody, or withdrawal change. Rates are not treated as evergreen facts. Readers should open the current docs before acting because a page can change after our review.
Limits and conflicts
Official docs can omit real-world support or outage issues. Audits do not guarantee that code is safe. A limited test does not prove all routes. Token Metrics may earn compensation from some links, but that does not set the conclusion. We do not accept a payment claim as evidence of safety or yield.
Worked examples
Liquid-staking depositor
We trace wallet signing, deposit contract, protocol accounting, liquid token, other apps that may hold the token, and exit. We flag each extra contract or market as a new layer. We do not describe a liquid token as cash or a fixed claim.
Node operator
We trace validator keys, withdrawal details, hardware, clients, updates, monitoring, bond or collateral, fees, penalties, and exit. A user who cannot maintain those duties is not a fit, even if the headline reward looks good.
Frequently asked questions
Why not rank by annual rate?
Rates change and do not show custody, liquidity, contract, penalty, or counterparty risk.
Does an audit make a protocol safe?
No. An audit is one input. Code, upgrades, operations, governance, and user actions still matter.
How are conflicts handled?
The page discloses possible compensation. Payment does not decide coverage or findings.
When should a page be updated?
After a material change or scheduled review. A user should still confirm current docs before acting.
Evidence review cadence and fail conditions
Repeat the evidence review whenever a platform changes its custody terms, validator set, withdrawal process, fee schedule, or supported assets. Save the official page, access date, and the exact statement used for each judgment so another reviewer can reproduce the result. Treat a missing or contradictory document as a failed check rather than filling the gap with marketing copy. Recheck a small withdrawal after material changes and record the elapsed steps, not a promised speed. Separate protocol risk from provider risk: a sound staking protocol does not remove account, key-management, counterparty, or interface risk. Finally, document why an option was excluded. That record makes future updates faster and prevents a high headline reward from overriding custody, liquidity, or evidence-quality failures.
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.
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
Editorial release gate
A page does not pass because it has links and headings. Each key finding needs a clear source and a plain limit. The page must name the user, the path, and the risk. It must also say when no sound rank can be made.
