Research methodology
How DeFiBeat turns assumptions into inspectable records.
The MVP treats each protocol, asset, market, monitor, finding, and dependency edge as static typed data. Pages render the evidence trail directly so review status and source coverage stay visible.
Protocols
22
3 fully reviewed.
Assets
19
Collateral records with issuer and redemption fields.
Dependency edges
198
Typed risk paths used for blast-radius views.
Severity model
5
Critical through informational findings.
Review status rubric
Status pills communicate coverage completeness, not endorsement.
| Status | Meaning |
|---|---|
| reviewed | All required fields, source links, and analyst findings are complete enough for the MVP. |
| partial | The record is useful but has known gaps in sources, dependencies, markets, or monitors. |
| under review | Research is actively being assembled and should not be treated as complete. |
| unreviewed | The entity exists in the registry but has not been reviewed. |
Risk dimensions
Each finding is tagged to a concrete risk surface.
| Dimension | What analysts look for |
|---|---|
| smart contract | Upgradeability, audits, proxy controls, and contract-level failure modes. |
| governance admin | Multisig, timelock, token vote, pause, parameter, and emergency control paths. |
| asset issuer | Issuer solvency, freeze powers, redemption promises, and off-chain custody assumptions. |
| bridge wrapper | Canonical bridge, third-party wrapper, lockbox, mint authority, and message security assumptions. |
| oracle | Price source, heartbeat, fallback, quorum, manipulation, and stale-price behavior. |
| chain settlement da | Settlement, data availability, validator, sequencer, and fraud or validity proof assumptions. |
| liquidity liquidation | Exit liquidity, liquidation depth, auction design, and bad-debt containment. |
| exposure concentration | Single collateral, issuer, bridge, chain, market, or governance concentration. |
| operational transparency | Public docs, source links, changelog coverage, monitor cadence, and incident disclosure. |
Dependency edge taxonomy
Edges make the graph queryable without hiding analyst judgment.
| Edge type | Interpretation |
|---|---|
| accepts collateral | A market or protocol can inherit risk from the collateral asset. |
| backs | An asset derives value from another asset, reserve, or backing basket. |
| bridged by | Availability or redemption depends on a bridge or wrapper path. |
| depends on | A generic dependency exists where a narrower edge is not expressive enough. |
| governed by | A protocol, asset, or contract is controlled by a governance process. |
| issued by | An asset is created, redeemed, or controlled by an issuer. |
| monitored by | A public or manual signal watches a dependency or parameter. |
| priced by | A market depends on an oracle or price adapter. |
| settles on | A protocol or asset deployment inherits settlement or data availability assumptions. |
| upgraded by | A proxy, owner, admin, or multisig can change deployed logic. |
| verified by | A fact is tied to verification or attestation infrastructure. |
| wraps | A token is a wrapper around another asset, bridge receipt, or vault position. |
Monitor taxonomy
Monitor rows describe signals, not guaranteed automated enforcement.
| Monitor status | Meaning |
|---|---|
| live | A public or deterministic signal is expected to be checked at the stated cadence. |
| planned | The signal is specified but ingestion or verification is not wired yet. |
| manual | The check requires analyst review, off-chain context, or a non-automated workflow. |
Source link policy
Evidence should be visible next to the claim it supports.
Entity sourcesProtocol and asset pages show source links beside the fact table.
Finding sourcesRisk findings carry their own source links because one entity can have many claims.
Review gateA reviewed status should require enough source coverage for another analyst to reproduce the claim.
ChangelogMaterial methodology or data-shape changes should be recorded in the public changelog.