FORESHOCK

Only protocols with enough independently verified data to trust a score appear here. This is a permanent rule, not a temporary gap.

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.

Kelp

Ethereum

low:

  • This methodology version hasn't been backtested against any historical incidents in this protocol's bucket yet.
  • This is not because this protocol's data is thin (80% of category weight is verified data).
Why this rating
Every category's contribution to the overall score, highest first.
Audit profile14.9Verified

1 audit on record, most recent audit is over 2 years old; the most recent audit found 3 High and 2 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.

Historical incidents12.7Verified

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

Dependency risk10.4Verified

Relies on 1 bridge.

Governance attack surface5.0Unverified

No verified evidence yet; held at the neutral midpoint rather than assumed safe or unsafe.

TVL profile3.5Verified

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

Code characteristics3.0Verified

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

Team factors2.5Unverified

No verified evidence yet; held at the neutral midpoint rather than assumed safe or unsafe.

Bug bounty2.5Unverified

No verified evidence yet; held at the neutral midpoint rather than assumed safe or unsafe.

Protocol age1.5Verified

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

Dependencies (1)

Relies on 1 bridge.

Incident history (1)
  • 2026-04-18 - LayerZero OFT bridge exploit ($293M lost)

    Still reflected in this protocol's assessment. Incident history does not expire under the methodology.

Audit history (0)

No audit history recorded.

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

Do you hold a position in this protocol?

Get an email when this assessment materially changes.