Risk & yield6 min read
Risk is a question, not a badge
Map the exact interaction, inspect change controls, and keep evidence gaps visible without inventing a safety score.
Research field guide / Web3
Web3 DeFi Meter
A risk reading, not a safety badge.
A Web3 DeFi Meter should show which dependencies you understand and which remain unresolved. Begin with the exact interaction, then inspect asset identity, contract evidence, change controls, and the intended exit. This is a read-only research framework, not an audit, certification, or security rating.
The question to ask
Which conditions must hold for this interaction to work as described?
Match the evidence to the system
Smart-contract security work includes several practices, from testing to audits and access controls. The useful question is what evidence applies to the deployed interaction you are considering. Record scope, excluded components, and unresolved findings rather than reducing the evidence to an audit badge.
Use evidence statuses, not safety percentages
Documented, partially documented, conflicting, and not established are statuses of your research. They are not probabilities of loss. A documented dependency can remain material. A count of answered questions measures checklist completion only and should not be repackaged as a safety score.
Ask one material question at a time
Prioritize gaps that could change the interpretation of the exact interaction. An unclear asset identifier or withdrawal condition deserves investigation before another unrelated metric is added. Keep conflicting documents with their versions and dates. Resolve the scope mismatch before adopting whichever description sounds more reassuring.
Primary reference: Ethereum: smart-contract security practices.
Your research checklist
Capture the fields that matter.
Keep identifiers, assumptions, and missing evidence next to the observation.
01
Interaction
Asset, contract, network, and intended outcome
Review the specific product rather than an umbrella brand.
02
Evidence
Version, deployment, scope, and observation date
A report about different code may not answer the deployment question.
03
Controls
Who can change critical rules and by what process
A control label does not explain its actual configuration.
04
Exit path
Documented procedure, conditions, and assumptions
A process description is not a guarantee of market execution.
Practical questions
Know the limits
of the reading.
Does an audit remove contract risk?
No. A review has a defined scope and cannot establish the absence of every possible problem. Record what was reviewed and what remains outside the evidence.
Should unknown fields count as neutral?
No. Preserve unknowns explicitly. A neutral-looking indicator could misleadingly imply that a question was assessed and found unimportant.
Continue your research
Related field notes
Network research6 min read
Bitcoin exposure is not one thing
Trace the relationship between native BTC, represented assets, reported backing, and the actual exit process.
Market analysis6 min read
A better research routine starts here
Build a repeatable read-only routine that checks freshness, preserves context, and separates observations from explanations.