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.

Euler V1

Euler V1 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 excluded from the reading, never counted as safe.
  • Validation: measured against 8 comparable incidents/controls in this protocol's TVL, age and category bucket.
In short

Foreshock's independent reading of Euler V1 is Elevated risk, 51.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. 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 Euler V1 safe?
Foreshock does not answer that as a yes or a no. Its independent reading of Euler V1 is Elevated risk, 51.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 Euler V1 been audited?
4 audits on record, most recent audit is over 2 years 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. An audit describes the code at the time it was reviewed. It is not a statement that the protocol is safe today.
Who controls Euler V1?
Admin key: 4/8 multisig (requires 4 of 8 keys to act), open source. Top 10 holders control 47.73%, adjusted figure may still include pooled custody (untagged exchanges, infrastructure contracts) due to tagging coverage limits; exclusions require positive identification.
Has Euler V1 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 Euler V1 assessment last updated?
6 September 2026. Readings are recomputed as evidence changes, and every category carries the date of the evidence behind it.
Score by categories
Historical incidents12.8

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

Audit profile8.0

4 audits on record, most recent audit is over 2 years 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.

Code characteristics6.8

Admin key: 4/8 multisig (requires 4 of 8 keys to act), open source.

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.

Governance attack surface5.0

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

Bug bounty3.2

No bug bounty program on record.

Team factors1.7

Doxxed team, track record: mixed.

Protocol age1.5

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

Assets held (2)

Available with a plan. See pricing.

Dependencies (1)

Available with a plan. See pricing.

Incident history (2)

Available with a plan. See pricing.

Audit history (4)

Available with a plan. See pricing.

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

Get told when this changesBrowse every protocol