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.

Revert Lend

Revert Lend 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 16 comparable incidents/controls in this protocol's TVL, age and category bucket.
In short

Foreshock's independent reading of Revert Lend is Elevated risk, 60.0 out of 100, as of 10 September 2026. The largest single contributor to that reading is audit profile: 1 audit on record, most recent audit is over 2 years old; the most recent audit found 6 High and 27 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. 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 Revert Lend safe?
Foreshock does not answer that as a yes or a no. Its independent reading of Revert Lend is Elevated risk, 60.0 out of 100, as of 10 September 2026, led by audit profile: 1 audit on record, most recent audit is over 2 years old; the most recent audit found 6 High and 27 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. The score and the reasoning are published in full so the reading can be checked rather than trusted.
Has Revert Lend been audited?
1 audit on record, most recent audit is over 2 years old; the most recent audit found 6 High and 27 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 Revert Lend?
Admin key: 48h timelock in place, open source. No governance token; control sits with timelock rather than a vote, so decision rights are concentrated rather than capturable. The form of that key is scored separately under code characteristics.
Has Revert Lend 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 Revert Lend assessment last updated?
10 September 2026. Readings are recomputed as evidence changes, and every category carries the date of the evidence behind it.
Score by categories
Audit profile17.1

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

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

Dependency risk9.8

Uses 2 oracles (Revert Lend is an oracle CONSUMER: it reads prices to value collateral and publishes none. Its V3Oracle combines Chainlink and Uniswap V3 TWAP as primary plus cross-check rather than averaging them, with modes CHAINLINK_TWAP_VERIFY, TWAP_CHAINLINK_VERIFY, CHAINLINK and TWAP, and _requireMaxDifference reverts the transaction when the two diverge beyond a configured maximum. Uniswap V3 exposure is structural rather than optional: the collateral is a Uniswap V3 position NFT.), composable with 3 other protocols.

Governance attack surface7.1

No governance token; control sits with timelock rather than a vote, so decision rights are concentrated rather than capturable. The form of that key is scored separately under code characteristics.

TVL profile3.6

TVL change (-21%) is within a stable range.

Bug bounty3.3

No bug bounty program on record.

Code characteristics3.0

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

Team factors1.8

Doxxed team, track record: unknown.

Protocol age1.5

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

Assets held (5)

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 (1)

Available with a plan. See pricing.

Also covered on Multi-Chain

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 Revert Lend 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