Sato Hub
← Balancer verification record

Score history

Balancer

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

41

Change over 57d

+12

Days measured

57

Days missed

0

Sato Score, daily

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

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

DateFromToChangeCause
2026-09-012941+12Sato 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 transparency16/20
20
Interface verifiability0/10
10
Docs & demo0/10
10
Listing transparency & provenance5/15
15
Independent verification0/10
10

The observed record

22.8% 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: 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-1341MediumActiveup
2026-09-1241MediumActiveup
2026-09-1141MediumActiveup
2026-09-1041MediumActiveup
2026-09-0941MediumActiveup
2026-09-0841MediumActiveup
2026-09-0741MediumActiveup
2026-09-0641MediumActiveup
2026-09-0541MediumActiveup
2026-09-0441MediumActiveup
2026-09-0341MediumActiveup
2026-09-0241MediumActiveup
2026-09-0141MediumActiveup
2026-08-3129LowActiveunknown
2026-08-3029LowActiveunknown
2026-08-2929LowActiveunknown
2026-08-2829LowActiveunknown
2026-08-2729LowActiveunknown
2026-08-2629LowActiveunknown
2026-08-2529LowActiveunknown
2026-08-2429LowActiveunknown
2026-08-2329LowActiveunknown
2026-08-2229LowActiveunknown
2026-08-2129LowActiveunknown
2026-08-2029LowActiveunknown
2026-08-1929LowActiveunknown
2026-08-1829LowActiveunknown
2026-08-1729LowActiveunknown
2026-08-1629LowActiveunknown
2026-08-1529LowActiveunknown
2026-08-1429LowActiveunknown
2026-08-1329LowActiveunknown
2026-08-1229LowActiveunknown
2026-08-1129LowActiveunknown
2026-08-1029LowActiveunknown
2026-08-0929LowActiveunknown
2026-08-0829LowActiveunknown
2026-08-0729LowActiveunknown
2026-08-0629LowActiveunknown
2026-08-0529LowActiveunknown
2026-08-0429LowActiveunknown
2026-08-0329LowActiveunknown
2026-08-0229LowActiveunknown
2026-08-0129LowActiveunknown
2026-07-3129LowActiveunknown
2026-07-3029LowActiveunknown
2026-07-2929LowActiveunknown
2026-07-2829LowActiveunknown
2026-07-2729LowActiveunknown
2026-07-2629LowActiveunknown
2026-07-2529LowActiveunknown
2026-07-2429LowActiveunknown
2026-07-2329LowActiveunknown
2026-07-2229LowActiveunknown
2026-07-2129LowActiveunknown
2026-07-2029LowActiveunknown
2026-07-1929LowActiveunknown

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 1, 2026
    Sato Score tier: Low → Medium
    Score 29 → 41.
  2. Jul 21, 2026
    Edited: onchain address
  3. Jul 19, 2026
    Edited: chains supported, description long
  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.
← Verification recordThis week’s moversDispute this score