Fast answer
Smart contract checks need contract address, approvals, upgrade path, admin controls, audit scope, exploit history, and revoke route.
Before interacting with a contract, record the official contract address, chain, function, approval amount, spender, admin or upgrade controls, audit scope, incident history, transaction hash, and revoke status.
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 before wallet interaction.
Contract address
Verify address from official sources before trusting a dapp, airdrop, or signal-room link.
Approval scope
Unlimited token approvals can remain dangerous after the original action is finished.
Upgrade controls
Upgradeable contracts and admin keys can change behavior after users deposit.
Audit scope
An audit does not prove every contract, deployment, integration, or future upgrade is safe.
Source context
Investor.gov warns crypto investors to exercise caution, while DeFi protocols expose contract and parameter surfaces.
CSR keeps smart-contract risk pages practical: users need address, approval, admin, and exit evidence before trusting a workflow.
Review standard
A reviewable smart-contract record proves what was signed and what remains approved.
For CSR evidence review, Crypto Smart Contract Risk 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.