Sato Hub
Score history

YO Protocol

One dated Sato Score reading per day. Days we changed the scoring method are marked. Not a safety or returns grade.

Score today

31

Change over 103d

+19

Days measured

103

Days missed

0

Sato Score, daily

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

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

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

DateFromToChangeCause
2026-10-102831+3Sato Hub changed the scoring method
2026-09-011628+12Sato Hub changed the scoring method
2026-07-201216+4Sato 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 transparency0/20
20
Interface verifiability0/10
10
Docs & demo0/10
10
Listing transparency & provenance4/15
15
Independent verification7/10
10

The observed record

100% of 59 daily checks since 2026-09-01 succeeded. This is the share of OUR checks that succeeded. It is not uptime: a failed check can be on our side. When a check before 2026-09-01 failed, the checks before that date are left out of the rate: the probe counted a bot-block as a failure then and recorded no reason for any failure.

2026-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 check2026-09-14: answered our check2026-09-15: answered our check2026-09-16: answered our check2026-09-17: answered our check2026-09-18: answered our check2026-09-19: answered our check2026-09-20: answered our check2026-09-21: answered our check2026-09-22: answered our check2026-09-23: answered our check2026-09-24: answered our check2026-09-25: answered our check2026-09-26: answered our check2026-09-27: answered our check2026-09-28: answered our check2026-09-29: answered our check2026-09-30: answered our check2026-10-01: answered our check2026-10-02: answered our check2026-10-03: answered our check2026-10-04: answered our check2026-10-05: answered our check2026-10-06: answered our check2026-10-07: answered our check2026-10-08: answered our check2026-10-09: answered our check2026-10-10: answered our check2026-10-11: answered our check2026-10-12: answered our check2026-10-13: answered our check2026-10-14: answered our check2026-10-15: answered our check2026-10-16: answered our check2026-10-17: answered our check2026-10-18: answered our check2026-10-19: answered our check2026-10-20: answered our check2026-10-21: answered our check2026-10-22: answered our check2026-10-23: answered our check2026-10-24: answered our check2026-10-25: answered our check2026-10-26: answered our check2026-10-27: answered our check2026-10-28: answered our check2026-10-29: 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-10-2931LowActiveup
2026-10-2831LowActiveup
2026-10-2731LowActiveup
2026-10-2631LowActiveup
2026-10-2531LowActiveup
2026-10-2431LowActiveup
2026-10-2331LowActiveup
2026-10-2231LowActiveup
2026-10-2131LowActiveup
2026-10-2031LowActiveup
2026-10-1931LowActiveup
2026-10-1831LowActiveup
2026-10-1731LowActiveup
2026-10-1631LowActiveup
2026-10-1531LowActiveup
2026-10-1431LowActiveup
2026-10-1331LowActiveup
2026-10-1231LowActiveup
2026-10-1131LowActiveup
2026-10-1031LowActiveup
2026-10-0928LowActiveup
2026-10-0828LowActiveup
2026-10-0728LowActiveup
2026-10-0628LowActiveup
2026-10-0528LowActiveup
2026-10-0428LowActiveup
2026-10-0328LowActiveup
2026-10-0228LowActiveup
2026-10-0128LowActiveup
2026-09-3028LowActiveup
2026-09-2928LowActiveup
2026-09-2828LowActiveup
2026-09-2728LowActiveup
2026-09-2628LowActiveup
2026-09-2528LowActiveup
2026-09-2428LowActiveup
2026-09-2328LowActiveup
2026-09-2228LowActiveup
2026-09-2128LowActiveup
2026-09-2028LowActiveup
2026-09-1928LowActiveup
2026-09-1828LowActiveup
2026-09-1728LowActiveup
2026-09-1628LowActiveup
2026-09-1528LowActiveup
2026-09-1428LowActiveup
2026-09-1328LowActiveup
2026-09-1228LowActiveup
2026-09-1128LowActiveup
2026-09-1028LowActiveup
2026-09-0928LowActiveup
2026-09-0828LowActiveup
2026-09-0728LowActiveup
2026-09-0628LowActiveup
2026-09-0528LowActiveup
2026-09-0428LowActiveup
2026-09-0328LowActiveup
2026-09-0228LowActiveup
2026-09-0128LowActiveup
2026-08-3116LowActiveunknown
2026-08-3016LowActiveunknown
2026-08-2916LowActiveunknown
2026-08-2816LowActiveunknown
2026-08-2716LowActiveunknown
2026-08-2616LowActiveunknown
2026-08-2516LowActiveunknown
2026-08-2416LowActiveunknown
2026-08-2316LowActiveunknown
2026-08-2216LowActiveunknown
2026-08-2116LowActiveunknown
2026-08-2016LowActiveunknown
2026-08-1916LowActiveunknown
2026-08-1816LowActiveunknown
2026-08-1716LowActiveunknown
2026-08-1616LowActiveunknown
2026-08-1516LowActiveunknown
2026-08-1416LowActiveunknown
2026-08-1316LowActiveunknown
2026-08-1216LowActiveunknown
2026-08-1116LowActiveunknown
2026-08-1016LowActiveunknown
2026-08-0916LowActiveunknown
2026-08-0816LowActiveunknown
2026-08-0716LowActiveunknown
2026-08-0616LowActiveunknown
2026-08-0516LowActiveunknown
2026-08-0416LowActiveunknown
2026-08-0316LowActiveunknown
2026-08-0216LowActiveunknown
2026-08-0116LowActiveunknown
2026-07-3116LowActiveunknown
2026-07-3016LowActiveunknown
2026-07-2916LowActiveunknown
2026-07-2816LowActiveunknown
2026-07-2716LowActiveunknown
2026-07-2616LowActiveunknown
2026-07-2516LowActiveunknown
2026-07-2416LowActiveunknown
2026-07-2316LowActiveunknown
2026-07-2216LowActiveunknown
2026-07-2116LowActiveunknown
2026-07-2016LowActiveunknown
2026-07-1912LowActiveunknown

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 1, 2026
    Sato Hub began tracking this listing
  2. Jul 21, 2026
    Edited: onchain address
  3. Jul 19, 2026
    Edited: chains supported
  4. Jul 19, 2026
    Listed on Sato Hub

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.