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.

Tonstakers LSD

Tonstakers LSD official site N/A

TON

:

  • 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: measured against 2 comparable incidents/controls in this protocol's TVL, age and category bucket.

Published 2026-09-25, unchanged since. Subscribers are told the day it changes.

Why this rating
Audit profile15.0
1 audit on record, most recent audit is over 2 years old; the most recent audit found 1 High and 4 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 characteristics9.8
Admin key: unknown, upgradeable without a meaningful timelock, open source.
Governance attack surface7.0
No governance token, and the controlling address could not be resolved, so this is scored as though control sits with an identified party. Immutability is only ever established by reading a contract with no owner and no upgrade path, never by failing to find one, so an unresolved controller is treated as a controller.
Dependency risk6.0
No bridge or oracle dependencies on record, composable with 5 other protocols. The exchange rate needs no oracle and this was verified in Tonstakers' own code rather than from prose: its SDK computes the rate as total_balance over supply read from the pool contract, with a forward projected rate alongside, so the rate is on-chain state and cannot be set by an admin.
Show the evidenceIts own FAQ frames the user-facing effect as rewards compounding every 18 hours. The real dependency is the VALIDATOR ARRANGEMENT, and it is permissioned. The designated docs describe an on-chain Approver that 'grants approvals to Controllers when they initiate an in-protocol borrowing request' and 'decides and enforces whether Pool validators follow decentralization and safety measures set by Governance', and validators 'can only request funds if approved by the Approver'. Validators deploy Controller contracts that borrow from the pool while elections are open and must repay principal plus a fixed premium; failure to repay after stake recovery halts the Controller pending a MANUAL governance decision. WHO ACTUALLY RUNS THOSE VALIDATORS IS NOT DISCLOSED ANYWHERE: the FAQ says only that stakers 'lend their tokens to trusted validators', and the validators page markets institutional clients and uptime without naming a single operator, publishing a whitelist or an address list. One further dependency worth recording because it affects anything built on the official SDK: tonapi.io, a third-party indexer, is hard-coded as the API endpoint and carries every read including the TON price. The designated docs' own risks page lists protocol logic issues, misbehaving-validator slashing, misbehaving-validator voting and TON network election delays.
TVL profile3.5
TVL change (4%) is within a stable range.
Bug bounty3.3
No bug bounty program on record.
Team factors3.0
Anonymous team, a weak but real signal on its own.
Historical incidents2.2
No known own or inherited incidents as of 25 September 2026.
Protocol age1.5
1100 days live, past the ~1yr floor; treated the same as any older protocol, not scored progressively safer with more age.
Dependencies (2)

Available with a plan. See pricing.

Incident history (0)

Available with a plan. See pricing.

Audit history (1)

Available with a plan. See pricing.

Common questions about Tonstakers LSD

Foreshock's independent reading of Tonstakers LSD is Elevated risk, 51.3 out of 100, as of 25 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 1 High and 4 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. 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 Tonstakers LSD safe?
Foreshock does not answer that as a yes or a no. Its independent reading of Tonstakers LSD is Elevated risk, 51.3 out of 100, as of 25 September 2026, led by audit profile: 1 audit on record, most recent audit is over 2 years old; the most recent audit found 1 High and 4 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 Tonstakers LSD been audited?
1 audit on record, most recent audit is over 2 years old; the most recent audit found 1 High and 4 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 Tonstakers LSD?
Admin key: unknown, upgradeable without a meaningful timelock, open source. No governance token, and the controlling address could not be resolved, so this is scored as though control sits with an identified party. Immutability is only ever established by reading a contract with no owner and no upgrade path, never by failing to find one, so an unresolved controller is treated as a controller.
Has Tonstakers LSD been exploited before?
No known own or inherited incidents as of 25 September 2026. Foreshock records an incident against a protocol whether it originated there or was inherited from something it depends on.
When was this Tonstakers LSD assessment last updated?
25 September 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

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 Tonstakers LSD 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