FORESHOCK

Protocols

Request coverage

Every protocol here carries a dated score and the share of it backed by independently verified evidence. Where that share is still thin the assessment says so, is marked Low-signal rather than given a risk band, and holds every unevidenced category at the neutral midpoint instead of assuming it safe. Every score and its reasoning are free to read; the underlying dependency, incident and audit records are part of a plan. Each reading here is fixed at the date beside it. Re-scoring never stops, but a changed reading reaches plan holders on the day it changes rather than this page, which is what a plan is for. How a score is built, how to read one, and how the rubric was tested against real exploits are all in the methodology.

Coverage grows three ways: protocols Foreshock selects at its own discretion, protocols requested through the Request coverage button, and sponsored assessments delivered on an agreed timeline. No path has a guaranteed date except sponsorship.

Scores run from 0, the safest reading, to 100, the riskiest, where 50 is the neutral midpoint every unverified category is held at. Red marks a protocol scoring 50 or above, the band called Elevated: worse than neutral on the evidence gathered. Amber marks one below it, called Moderate. The boundary is fixed. It does not move as coverage grows, and it is not fitted to any backtest result.

Compound V2

Compound V2 official site N/A

Ethereum

:

  • Evidence: this reading is based on 100% of the scored weight, verified against named sources. Categories without verified data are held at the neutral midpoint at their full weight, never counted as safe.
  • Validation: measured against 2 comparable incidents/controls in this protocol's TVL, age and category bucket.

Published 2026-09-06. Up-to-date reading and 1 change since for subscribers. See plans

Why this rating
Historical incidents12.8
This protocol has 1 prior incident of its own, hard floor applied regardless of current size/age.
Audit profile10.0
4 audits/contests on record, most recent (Trail of Bits, 2020-02-01) has unread findings, scored as unknown, not assumed clean.
TVL profile6.5
TVL is 99% below this protocol's own peak and has not recovered, so the revenue that funds audits, bounties and maintenance is largely gone while the contracts still hold value; TVL change (17%) is within a stable range.
Dependency risk6.0
Uses 1 oracle. Compound's own current docs: 'The Compound v2 Price Feed accounts price data for the protocol. The protocol's Comptroller contract uses it as a source of truth for prices. Prices are updated by Chainlink Price Feeds.' Compound originally built its own Uniswap-TWAP-based 'Open Price Feed' (per its own open-oracle repo and 2019 blog announcement); the live docs no longer describe that mechanism and now document Chainlink as the operative source.
Show the evidenceNo first-party page narrates the exact migration date. V2 is Ethereum-mainnet-only; no bridge dependency is described.
Governance attack surface5.0
Top 10 holders control 36.33%, adjusted figure may still include pooled custody (untagged exchanges, infrastructure contracts) due to tagging coverage limits; exclusions require positive identification.
Code characteristics3.0
Admin key: 48h timelock in place, open source.
Protocol age1.5
2679 days live, past the ~1yr floor; treated the same as any older protocol, not scored progressively safer with more age.
Team factors1.0
Doxxed team, track record: strong.
Bug bounty0.7
Has a bug bounty program, up to $1 000 000, hosted on Immunefi.
Assets held (5)

Available with a plan. See pricing.

Dependencies (1)

Available with a plan. See pricing.

Incident history (1)

Available with a plan. See pricing.

Audit history (4)

Available with a plan. See pricing.

Common questions about Compound V2

Foreshock's independent reading of Compound V2 is Moderate risk, 46.5 out of 100, as of 6 September 2026. The largest single contributor to that reading is historical incidents: this protocol has 1 prior incident of its own, hard floor applied regardless of current size/age. All nine scored categories are backed by verified evidence. This published reading is fixed at that date. Re-scoring never stops, and when a reading changes it reaches plan holders on the day it changes rather than this page. Foreshock publishes the reading and the reasoning behind it. It is not a verdict on whether to use this protocol, and it is not investment advice.

Is Compound V2 safe?
Foreshock does not answer that as a yes or a no. Its independent reading of Compound V2 is Moderate risk, 46.5 out of 100, as of 6 September 2026, led by historical incidents: this protocol has 1 prior incident of its own, hard floor applied regardless of current size/age. The score and the reasoning are published in full so the reading can be checked rather than trusted.
Has Compound V2 been audited?
4 audits/contests on record, most recent (Trail of Bits, 2020-02-01) has unread findings, scored as unknown, not assumed clean. An audit describes the code at the time it was reviewed. It is not a statement that the protocol is safe today.
Who controls Compound V2?
Admin key: 48h timelock in place, open source. Top 10 holders control 36.33%, adjusted figure may still include pooled custody (untagged exchanges, infrastructure contracts) due to tagging coverage limits; exclusions require positive identification.
Has Compound V2 been exploited before?
This protocol has 1 prior incident of its own, hard floor applied regardless of current size/age. Foreshock records an incident against a protocol whether it originated there or was inherited from something it depends on.
When was this Compound V2 assessment last updated?
6 September 2026, and that date does not move on its own. A reading published here is fixed when it is published; re-scoring never stops, and a changed reading reaches plan holders on the day it changes rather than this page. Every category carries the date of the evidence behind it.
Also covered on Ethereum

This assessment follows Foreshock's published methodology. Exact category weights, scoring rules, thresholds, and aggregation logic are proprietary and not shown here. How to interpret this assessment

This reading will change.

This reading is fixed at the date above it, and it stays there. We keep re-scoring Compound V2 as the evidence moves, a new audit, a changed admin control, an incident, and this page is free to read and always will be. The updated reading is what a plan buys: you are told by email on the day it changes, instead of finding out the next time you happen to look.

Pick one protocol and get a free weekly summary of what changed. Same-day alerts come with a plan.

Monitor this protocolGet told when this changesBrowse every protocol