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.

OnRe

OnRe official site N/A

Solana

:

  • 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: the rubric is backtested against past exploits of protocols in the same TVL, age and category bucket. Protocols of this scale and kind have no such history - a limit of the record itself, not unfinished work.

Published 2026-10-16, unchanged since. Subscribers are told the day it changes.

Why this rating
Dependency risk9.0
Uses 1 oracle, composable with 5 other protocols. Read 2026-10-16. OnRe's docs say NAV used for minting and redemption is computed inside the contract from base price, annual rate and a time component, and that Pyth and Chainlink feeds exist in the wider stack for integrators and are not on the issuance or redemption path.
Show the evidenceA search of the onre-sol program source (commit c049083) finds no Pyth, Chainlink, Switchboard or oracle reference. The price curve is nonetheless set by the boss role, so it is recorded as one governance-set value of type other (Sky RWA precedent). NAV is not read from the underlying reinsurance accounts on chain.
Code characteristics9.0
Admin key: 4/7 multisig (requires 4 of 7 keys to act), upgradeable without a meaningful timelock, open source.
Governance attack surface7.0
No governance token; control sits with multisig 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.5
TVL change (-3%) is within a stable range.
Historical incidents2.3
No known own or inherited incidents as of 16 October 2026.
Audit profile2.0
6 audits on record, most recent audit is recent (<=180d); the most recent audit found 0 High and 1 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.8
Doxxed team, track record: unknown.
Protocol age1.5
459 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 $100 000, hosted on Immunefi.
Assets held (1)

Available with a plan. See pricing.

Dependencies (2)

Available with a plan. See pricing.

Incident history (0)

Available with a plan. See pricing.

Audit history (6)

Available with a plan. See pricing.

Common questions about OnRe

Foreshock's independent reading of OnRe is Moderate risk, 37.3 out of 100, as of 16 October 2026. The largest single contributor to that reading is code characteristics: admin key: 4/7 multisig (requires 4 of 7 keys to act), upgradeable without a meaningful timelock, open source. 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 OnRe safe?
Foreshock does not answer that as a yes or a no. Its independent reading of OnRe is Moderate risk, 37.3 out of 100, as of 16 October 2026, led by code characteristics: admin key: 4/7 multisig (requires 4 of 7 keys to act), upgradeable without a meaningful timelock, open source. The score and the reasoning are published in full so the reading can be checked rather than trusted.
Has OnRe been audited?
6 audits on record, most recent audit is recent (<=180d); the most recent audit found 0 High and 1 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 OnRe?
Admin key: 4/7 multisig (requires 4 of 7 keys to act), upgradeable without a meaningful timelock, open source. No governance token; control sits with multisig rather than a vote, so decision rights are concentrated rather than capturable. The form of that key is scored separately under code characteristics.
Has OnRe been exploited before?
No known own or inherited incidents as of 16 October 2026. Foreshock records an incident against a protocol whether it originated there or was inherited from something it depends on.
When was this OnRe assessment last updated?
16 October 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 Solana

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