FORESHOCK

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. 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.

Fluid Lending

Fluid Lending official site N/A

Multi-Chain

:

  • Evidence: this reading is based on 100% of the scored weight, verified against named sources. Categories without verified data are excluded from the reading, never counted as safe.
  • Validation: measured against 7 comparable incidents/controls in this protocol's TVL, age and category bucket.
Score by categories
Historical incidents12.7

This protocol has 1 prior incident of its own, hard floor applied regardless of current size/age.

Dependency risk11.9

Uses 3 oracles (Fluid CONSUMES price data and does not publish it, and the interesting part is the redundancy design rather than the provider list. Its own natspec documents a UniV3CheckCLRSOracle -- 'UniswapV3 checked against Chainlink / Redstone Oracle' -- whose _RATE_SOURCE immutable selects between UniV3 only, UniV3 checked against Chainlink or RedStone, or Chainlink/RedStone checked against UniV3, with TWAP windows of 240/60/15/1 seconds. A separate FallbackCLRSOracle gives Chainlink with RedStone fallback or the reverse. So a market can be configured with genuine cross-source checking, but 'UniV3 ONLY (no check)' is also a valid configuration. Its deployment manifest carries 321 oracle entries. The composability exposure is direct and documented: the capped-rate family reads sUSDe and sUSDS contracts by address, with capping as the stated mitigation.), composable with 4 other protocols.

Governance attack surface7.5

Top 10 holders control 56%, adjusted figure may still include pooled custody (untagged exchanges, infrastructure contracts) due to tagging coverage limits; exclusions require positive identification.

TVL profile3.5

TVL change (13%) is within a stable range.

Code characteristics3.0

Admin key: 24h timelock in place, open source.

Audit profile2.0

4 audits on record, most recent audit is 6-12 months old; the most recent audit found 0 High and 0 Medium severity issues. This reflects code quality at the time of that audit only, not a claim that these specific issues are still unresolved today.

Team factors1.7

Doxxed team, track record: unknown.

Protocol age1.5

922 days live, past the ~1yr floor; treated the same as any older protocol, not scored progressively safer with more age.

Bug bounty1.2

Has a bug bounty program, up to $500 000, hosted on Immunefi.

Assets held (7)

Available with a plan. See pricing.

Dependencies (2)

Available with a plan. See pricing.

Incident history (1)

Available with a plan. See pricing.

Audit history (4)

Available with a plan. See pricing.

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