Sato Hub
← DefiLlama verification record

Score history

DefiLlama

Every Sato Hub Sato Score reading we have captured for this listing, one per day, each dated. Days we changed the scoring method are marked separately from days the project moved. How open, active and verifiable — not a safety, quality, or returns grade.

Score today

75

Change over 90d

+5

Days measured

90

Days missed

4

Sato Score, daily

2026-06-11 → 2026-09-13
02550751002026-06-25: Sato Hub changed the scoring method (71 → 73). Not a change by the project.2026-07-14: Sato Hub changed the scoring method (73 → 75). Not a change by the project.2026-06-12: 70 (High)2026-06-13: 70 (High)2026-06-14: 70 (High)2026-06-15: 70 (High)2026-06-16: 70 (High)2026-06-17: 70 (High)2026-06-18: 71 (High)2026-06-19: 71 (High)2026-06-20: 71 (High)2026-06-22: 71 (High)2026-06-24: 71 (High)2026-06-25: 73 (High)2026-06-26: 73 (High)2026-06-27: 73 (High)2026-06-30: 73 (High)2026-07-01: 73 (High)2026-07-02: 73 (High)2026-07-03: 73 (High)2026-07-04: 73 (High)2026-07-05: 73 (High)2026-07-06: 73 (High)2026-07-07: 73 (High)2026-07-08: 73 (High)2026-07-09: 73 (High)2026-07-10: 73 (High)2026-07-11: 73 (High)2026-07-12: 73 (High)2026-07-13: 73 (High)2026-07-14: 75 (High)2026-07-15: 75 (High)2026-07-16: 75 (High)2026-07-17: 75 (High)2026-07-18: 75 (High)2026-07-19: 75 (High)2026-07-20: 75 (High)2026-07-21: 75 (High)2026-07-22: 75 (High)2026-07-23: 75 (High)2026-07-24: 75 (High)2026-07-25: 75 (High)2026-07-26: 75 (High)2026-07-27: 75 (High)2026-07-28: 75 (High)2026-07-29: 75 (High)2026-07-30: 75 (High)2026-07-31: 75 (High)2026-08-01: 75 (High)2026-08-02: 75 (High)2026-08-03: 75 (High)2026-08-04: 75 (High)2026-08-05: 75 (High)2026-08-06: 75 (High)2026-08-07: 75 (High)2026-08-08: 75 (High)2026-08-09: 75 (High)2026-08-10: 75 (High)2026-08-11: 75 (High)2026-08-12: 75 (High)2026-08-13: 75 (High)2026-08-14: 75 (High)2026-08-15: 75 (High)2026-08-16: 75 (High)2026-08-17: 75 (High)2026-08-18: 75 (High)2026-08-19: 75 (High)2026-08-20: 75 (High)2026-08-21: 75 (High)2026-08-22: 75 (High)2026-08-23: 75 (High)2026-08-24: 75 (High)2026-08-25: 75 (High)2026-08-26: 75 (High)2026-08-27: 75 (High)2026-08-28: 75 (High)2026-08-29: 75 (High)2026-08-30: 75 (High)2026-08-31: 75 (High)2026-09-01: 75 (High)2026-09-02: 75 (High)2026-09-03: 75 (High)2026-09-04: 75 (High)2026-09-05: 75 (High)2026-09-06: 75 (High)2026-09-07: 75 (High)2026-09-08: 75 (High)2026-09-09: 75 (High)2026-09-10: 75 (High)2026-09-11: 75 (High)2026-09-12: 75 (High)2026-09-13: 75 (High)7075752026-06-122026-09-13

4 days in this span have no reading; the line breaks there rather than joining across them. A dashed vertical mark (┆) is a day Sato Hub changed the scoring method — movement on those days is ours, not the project’s.

Every day the score moved

1 change attributable to the project, 2 caused by a revision of the scoring method.

DateFromToChangeCause
2026-07-147375+2Sato Hub changed the scoring method
2026-06-257173+2Sato Hub changed the scoring method
2026-06-187071+1the project

What moved, component by component

Six charts, six axes — each scaled to its own maximum weight. They are never stacked on one axis: a component worth 10 points and one worth 35 would not be comparable on a shared scale, and the small one is usually the one that moved.

Maintenance & liveness35/35
35
Code transparency16/20
20
Interface verifiability8/10
10
Docs & demo6/10
10
Listing transparency & provenance10/15
15
Independent verification0/10
10

The observed record

21% of Sato Hub's own daily checks succeeded over 62 checks. This is the share of OUR checks that succeeded. It is not uptime: a failed check can be on our side, and before 2026-09-01 no failure recorded why.

2026-07-14: failed, unattributable2026-07-15: failed, unattributable2026-07-16: failed, unattributable2026-07-17: failed, unattributable2026-07-18: failed, unattributable2026-07-19: failed, unattributable2026-07-20: failed, unattributable2026-07-21: failed, unattributable2026-07-22: failed, unattributable2026-07-23: failed, unattributable2026-07-24: failed, unattributable2026-07-25: failed, unattributable2026-07-26: failed, unattributable2026-07-27: failed, unattributable2026-07-28: failed, unattributable2026-07-29: failed, unattributable2026-07-30: failed, unattributable2026-07-31: failed, unattributable2026-08-01: failed, unattributable2026-08-02: failed, unattributable2026-08-03: failed, unattributable2026-08-04: failed, unattributable2026-08-05: failed, unattributable2026-08-06: failed, unattributable2026-08-07: failed, unattributable2026-08-08: failed, unattributable2026-08-09: failed, unattributable2026-08-10: failed, unattributable2026-08-11: failed, unattributable2026-08-12: failed, unattributable2026-08-13: failed, unattributable2026-08-14: failed, unattributable2026-08-15: failed, unattributable2026-08-16: failed, unattributable2026-08-17: failed, unattributable2026-08-18: failed, unattributable2026-08-19: failed, unattributable2026-08-20: failed, unattributable2026-08-21: failed, unattributable2026-08-22: failed, unattributable2026-08-23: failed, unattributable2026-08-24: failed, unattributable2026-08-25: failed, unattributable2026-08-26: failed, unattributable2026-08-27: failed, unattributable2026-08-28: failed, unattributable2026-08-29: failed, unattributable2026-08-30: failed, unattributable2026-08-31: failed, unattributable2026-09-01: answered our check2026-09-02: answered our check2026-09-03: answered our check2026-09-04: answered our check2026-09-05: answered our check2026-09-06: answered our check2026-09-07: answered our check2026-09-08: answered our check2026-09-09: answered our check2026-09-10: answered our check2026-09-11: answered our check2026-09-12: answered our check2026-09-13: answered our check
  • answered
  • host answered with an error
  • failed on our side
  • failed, unattributable

Every reading

The table the charts are drawn from. A missing day is missing from this table too — nothing is filled in.

DateScoreTierStatusOur check
2026-09-1375HighActiveup
2026-09-1275HighActiveup
2026-09-1175HighActiveup
2026-09-1075HighActiveup
2026-09-0975HighActiveup
2026-09-0875HighActiveup
2026-09-0775HighActiveup
2026-09-0675HighActiveup
2026-09-0575HighActiveup
2026-09-0475HighActiveup
2026-09-0375HighActiveup
2026-09-0275HighActiveup
2026-09-0175HighActiveup
2026-08-3175HighActiveunknown
2026-08-3075HighActiveunknown
2026-08-2975HighActiveunknown
2026-08-2875HighActiveunknown
2026-08-2775HighActiveunknown
2026-08-2675HighActiveunknown
2026-08-2575HighActiveunknown
2026-08-2475HighActiveunknown
2026-08-2375HighActiveunknown
2026-08-2275HighActiveunknown
2026-08-2175HighActiveunknown
2026-08-2075HighActiveunknown
2026-08-1975HighActiveunknown
2026-08-1875HighActiveunknown
2026-08-1775HighActiveunknown
2026-08-1675HighActiveunknown
2026-08-1575HighActiveunknown
2026-08-1475HighActiveunknown
2026-08-1375HighActiveunknown
2026-08-1275HighActiveunknown
2026-08-1175HighActiveunknown
2026-08-1075HighActiveunknown
2026-08-0975HighActiveunknown
2026-08-0875HighActiveunknown
2026-08-0775HighActiveunknown
2026-08-0675HighActiveunknown
2026-08-0575HighActiveunknown
2026-08-0475HighActiveunknown
2026-08-0375HighActiveunknown
2026-08-0275HighActiveunknown
2026-08-0175HighActiveunknown
2026-07-3175HighActiveunknown
2026-07-3075HighActiveunknown
2026-07-2975HighActiveunknown
2026-07-2875HighActiveunknown
2026-07-2775HighActiveunknown
2026-07-2675HighActiveunknown
2026-07-2575HighActiveunknown
2026-07-2475HighActiveunknown
2026-07-2375HighActiveunknown
2026-07-2275HighActiveunknown
2026-07-2175HighActiveunknown
2026-07-2075HighActiveunknown
2026-07-1975HighActiveunknown
2026-07-1875HighActiveunknown
2026-07-1775HighActiveunknown
2026-07-1675HighActiveunknown
2026-07-1575HighActiveunknown
2026-07-1475HighActiveunknown
2026-07-1373HighActivenot checked
2026-07-1273HighActivenot checked
2026-07-1173HighActivenot checked
2026-07-1073HighActivenot checked
2026-07-0973HighActivenot checked
2026-07-0873HighActivenot checked
2026-07-0773HighActivenot checked
2026-07-0673HighActivenot checked
2026-07-0573HighActivenot checked
2026-07-0473HighActivenot checked
2026-07-0373HighActivenot checked
2026-07-0273HighActivenot checked
2026-07-0173HighActivenot checked
2026-06-3073HighActivenot checked
2026-06-2773HighActivenot checked
2026-06-2673HighActivenot checked
2026-06-2573HighActivenot checked
2026-06-2471HighActivenot checked
2026-06-2271HighActivenot checked
2026-06-2071HighActivenot checked
2026-06-1971HighActivenot checked
2026-06-1871HighActivenot checked
2026-06-1770HighActivenot checked
2026-06-1670HighActivenot checked
2026-06-1570HighActivenot checked
2026-06-1470HighActivenot checked
2026-06-1370HighActivenot checked
2026-06-1270HighActivenot checked
2026-06-11unknown—Activenot checked

What happened alongside it

Releases, status changes, applied corrections and answered disputes, on the same dates — so a movement in the line can be read against an event rather than guessed at.

  1. Sep 7, 2026
    Verified: deploy spec
  2. Jun 25, 2026
    Enriched: deployment options
  3. Jun 12, 2026
    Sato Hub began tracking this listing

How to read this

  • · Every point is one UTC day. A day we did not capture is drawn as a gap, never joined across.
  • · A change on a marked methodology day is ours, not the project’s.
  • · The score says how open, active and verifiable the project is. It is not a safety, quality or returns grade.
  • · The inputs behind today’s score are published at /api/export/score-inputs.json and the arithmetic is reproducible on your own machine.
← Verification recordThis week’s moversDispute this score