Fast answer
Staking slashing checks need validator, operator, slashable behavior, penalty history, correlated risk, and final balance evidence.
Before staking or restaking, identify who can trigger penalties, what behavior is slashable, whether penalties are socialized, how alerts are handled, and how final balances are reconciled.
No guaranteed yield exists; staking, lending, liquidity provision, and reward programs all need lockup, smart-contract, market, liquidity, tax, and withdrawal-risk checks.
Yield checks
What to inspect in slashing risk.
Validator behavior
Record uptime, double-signing controls, client diversity, and operator incident history where available.
Penalty mechanics
Separate minor offline penalties from slashing and ejection conditions.
Socialized loss
Pooling or liquid staking can spread validator losses across participants depending on protocol rules.
Restaking layer
Additional services can add new slashing assumptions beyond base staking.
Source context
Ethereum proof-of-stake docs explain penalties, slashing, and correlation penalties.
CSR treats slashing as a required risk field in staking and restaking reviews, not as an edge case to hide below APY.
Review standard
A reviewable staking file shows how penalties are detected and recorded.
For CSR evidence review, Crypto Staking Slashing Guide records should preserve asset, chain, protocol, wallet or exchange, reward source, fee, lockup or withdrawal rule, smart-contract exposure, slashing or liquidation rule, transaction hash, and final outcome.