Version history
Every immutable snapshot of Summer.fi. A new version is saved each time the page changes, with the reason it changed. Pick two versions to see exactly what changed.
- v5currentTrust score: 332026-10-17 02:57:29Z
Community evidenceA moderator rejected a piece of community-submitted evidence: signals.same_url_accepted_for_page shows this exact The Block URL is already accepted as evidence on the Summer.fi page (id f1482e2b-bb67-4f1e-83dd-0ccce29df493). Trust score now 33.
hash: 8Hcrvpwhicic…changes from v4 - v4Trust score: 332026-10-16 22:57:29Z
Community evidenceA moderator rejected a piece of community-submitted evidence: signals.same_url_accepted_for_page shows the same normalised theblock.co link is already accepted on the Summer.fi page (submission f1482e2b-...). Trust score now 33.
hash: 5YMxqLXAiPwU…changes from v3 - v3Trust score: 332026-10-16 20:29:53Z
Community evidenceA moderator accepted a piece of community-submitted evidence: CoinDesk confirms the ~$6M Lazy Summer vault exploit on July 6, 2026, early analyses citing a large flash loan reportedly sourced through Morpho, and that guardians paused the affected vaults, matching the note. Trust score now 33.
hash: AnDMVoXTgqB5…changes from v2 - v2Trust score: 352026-10-16 14:29:17Z
Community evidenceA moderator accepted a piece of community-submitted evidence: The Block confirms a ~$6M flash-loan exploit of Summer.fi's Lazy Summer Protocol on July 6, 2026, attributed by CertiK to a share-accounting (Fleet Commander/totalAssets) manipulation funded by a $65.4M flash loan -- matching the submission's claim. Trust score now 35.
hash: 4YzKbrQR6MDJ…changes from v1 - v1Trust score: 362026-10-10 18:41:38Z
Score recalculatedRescored under Scoring v2, the published formula (avoid.net/scoring): 25 → 36. Problems weighed by who is responsible: incidents the subject suffered −20, concerns that are not fraud −10, problems around the subject, caused by others −4.3; legitimacy credit long-running +10; no longer operating, so capped at 50; the penalty for incidents it suffered is capped at 20; a recent unresolved incident −13.8.
hash: cb10b8d1be89…