Sato Hub
OnchainKit verification record

Score history

OnchainKit

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

62

Change over 57d

+21

Days measured

57

Days missed

0

Sato Score, daily

2026-07-192026-09-13
02550751002026-07-20: Sato Hub changed the scoring method (41 → 42). Not a change by the project.2026-09-01: Sato Hub changed the scoring method (59 → 62). Not a change by the project.2026-07-19: 41 (Medium)2026-07-20: 42 (Medium)2026-07-21: 46 (Medium)2026-07-22: 46 (Medium)2026-07-23: 46 (Medium)2026-07-24: 46 (Medium)2026-07-25: 46 (Medium)2026-07-26: 46 (Medium)2026-07-27: 46 (Medium)2026-07-28: 46 (Medium)2026-07-29: 46 (Medium)2026-07-30: 46 (Medium)2026-07-31: 46 (Medium)2026-08-01: 46 (Medium)2026-08-02: 59 (Medium)2026-08-03: 59 (Medium)2026-08-04: 59 (Medium)2026-08-05: 59 (Medium)2026-08-06: 59 (Medium)2026-08-07: 59 (Medium)2026-08-08: 59 (Medium)2026-08-09: 59 (Medium)2026-08-10: 59 (Medium)2026-08-11: 59 (Medium)2026-08-12: 59 (Medium)2026-08-13: 59 (Medium)2026-08-14: 59 (Medium)2026-08-15: 59 (Medium)2026-08-16: 59 (Medium)2026-08-17: 59 (Medium)2026-08-18: 59 (Medium)2026-08-19: 59 (Medium)2026-08-20: 59 (Medium)2026-08-21: 59 (Medium)2026-08-22: 59 (Medium)2026-08-23: 59 (Medium)2026-08-24: 59 (Medium)2026-08-25: 59 (Medium)2026-08-26: 59 (Medium)2026-08-27: 59 (Medium)2026-08-28: 59 (Medium)2026-08-29: 59 (Medium)2026-08-30: 59 (Medium)2026-08-31: 59 (Medium)2026-09-01: 62 (Medium)2026-09-02: 62 (Medium)2026-09-03: 62 (Medium)2026-09-04: 62 (Medium)2026-09-05: 62 (Medium)2026-09-06: 62 (Medium)2026-09-07: 62 (Medium)2026-09-08: 62 (Medium)2026-09-09: 62 (Medium)2026-09-10: 62 (Medium)2026-09-11: 62 (Medium)2026-09-12: 62 (Medium)2026-09-13: 62 (Medium)4162622026-07-192026-09-13

Every day in this span has a reading. 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

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

DateFromToChangeCause
2026-09-015962+3Sato Hub changed the scoring method
2026-08-024659+13the project
2026-07-214246+4the project
2026-07-204142+1Sato Hub changed the scoring method

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 & liveness20/35
35
Code transparency20/20
20
Interface verifiability0/10
10
Docs & demo6/10
10
Listing transparency & provenance13/15
15
Independent verification3/10
10

The observed record

100% of Sato Hub's own daily checks succeeded over 57 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-19: answered our check2026-07-20: answered our check2026-07-21: answered our check2026-07-22: answered our check2026-07-23: answered our check2026-07-24: answered our check2026-07-25: answered our check2026-07-26: answered our check2026-07-27: answered our check2026-07-28: answered our check2026-07-29: answered our check2026-07-30: answered our check2026-07-31: answered our check2026-08-01: answered our check2026-08-02: answered our check2026-08-03: answered our check2026-08-04: answered our check2026-08-05: answered our check2026-08-06: answered our check2026-08-07: answered our check2026-08-08: answered our check2026-08-09: answered our check2026-08-10: answered our check2026-08-11: answered our check2026-08-12: answered our check2026-08-13: answered our check2026-08-14: answered our check2026-08-15: answered our check2026-08-16: answered our check2026-08-17: answered our check2026-08-18: answered our check2026-08-19: answered our check2026-08-20: answered our check2026-08-21: answered our check2026-08-22: answered our check2026-08-23: answered our check2026-08-24: answered our check2026-08-25: answered our check2026-08-26: answered our check2026-08-27: answered our check2026-08-28: answered our check2026-08-29: answered our check2026-08-30: answered our check2026-08-31: answered our check2026-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-1362MediumActiveup
2026-09-1262MediumActiveup
2026-09-1162MediumActiveup
2026-09-1062MediumActiveup
2026-09-0962MediumActiveup
2026-09-0862MediumActiveup
2026-09-0762MediumActiveup
2026-09-0662MediumActiveup
2026-09-0562MediumActiveup
2026-09-0462MediumActiveup
2026-09-0362MediumActiveup
2026-09-0262MediumActiveup
2026-09-0162MediumActiveup
2026-08-3159MediumActiveup
2026-08-3059MediumActiveup
2026-08-2959MediumActiveup
2026-08-2859MediumActiveup
2026-08-2759MediumActiveup
2026-08-2659MediumActiveup
2026-08-2559MediumActiveup
2026-08-2459MediumActiveup
2026-08-2359MediumActiveup
2026-08-2259MediumActiveup
2026-08-2159MediumActiveup
2026-08-2059MediumActiveup
2026-08-1959MediumActiveup
2026-08-1859MediumActiveup
2026-08-1759MediumActiveup
2026-08-1659MediumActiveup
2026-08-1559MediumActiveup
2026-08-1459MediumActiveup
2026-08-1359MediumActiveup
2026-08-1259MediumActiveup
2026-08-1159MediumActiveup
2026-08-1059MediumActiveup
2026-08-0959MediumActiveup
2026-08-0859MediumActiveup
2026-08-0759MediumActiveup
2026-08-0659MediumActiveup
2026-08-0559MediumActiveup
2026-08-0459MediumActiveup
2026-08-0359MediumActiveup
2026-08-0259MediumActiveup
2026-08-0146MediumActiveup
2026-07-3146MediumActiveup
2026-07-3046MediumActiveup
2026-07-2946MediumActiveup
2026-07-2846MediumActiveup
2026-07-2746MediumActiveup
2026-07-2646MediumActiveup
2026-07-2546MediumActiveup
2026-07-2446MediumActiveup
2026-07-2346MediumActiveup
2026-07-2246MediumActiveup
2026-07-2146MediumActiveup
2026-07-2042MediumActiveup
2026-07-1941MediumActiveup

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. Aug 2, 2026
    Auto-enriched: docs url, x url, creator name, tags
  2. Jul 20, 2026
    Edited: deploy spec
  3. Jul 19, 2026
    Edited: website url
  4. Jul 19, 2026
    Listed on Sato Hub
  5. Jul 19, 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.