Sato Hub
← Virtuals Protocol verification record

Score history

Virtuals Protocol

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

78

Change over 90d

+13

Days measured

90

Days missed

4

Sato Score, daily

2026-06-11 → 2026-09-13
02550751002026-06-17: Sato Hub changed the scoring method (65 → 66). Not a change by the project.2026-06-25: Sato Hub changed the scoring method (66 → 72). Not a change by the project.2026-07-14: Sato Hub changed the scoring method (72 → 75). Not a change by the project.2026-07-20: Sato Hub changed the scoring method (75 → 79). Not a change by the project.2026-09-01: Sato Hub changed the scoring method (75 → 78). Not a change by the project.2026-06-12: 65 (Medium)2026-06-13: 65 (Medium)2026-06-14: 65 (Medium)2026-06-15: 65 (Medium)2026-06-16: 65 (Medium)2026-06-17: 66 (Medium)2026-06-18: 66 (Medium)2026-06-19: 66 (Medium)2026-06-20: 66 (Medium)2026-06-22: 66 (Medium)2026-06-24: 66 (Medium)2026-06-25: 72 (High)2026-06-26: 72 (High)2026-06-27: 72 (High)2026-06-30: 72 (High)2026-07-01: 72 (High)2026-07-02: 72 (High)2026-07-03: 72 (High)2026-07-04: 72 (High)2026-07-05: 72 (High)2026-07-06: 72 (High)2026-07-07: 72 (High)2026-07-08: 72 (High)2026-07-09: 72 (High)2026-07-10: 72 (High)2026-07-11: 72 (High)2026-07-12: 72 (High)2026-07-13: 72 (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: 79 (High)2026-07-21: 79 (High)2026-07-22: 79 (High)2026-07-23: 79 (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: 78 (High)2026-09-02: 78 (High)2026-09-03: 78 (High)2026-09-04: 78 (High)2026-09-05: 78 (High)2026-09-06: 78 (High)2026-09-07: 78 (High)2026-09-08: 78 (High)2026-09-09: 78 (High)2026-09-10: 78 (High)2026-09-11: 78 (High)2026-09-12: 78 (High)2026-09-13: 78 (High)6579782026-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, 5 caused by a revision of the scoring method.

DateFromToChangeCause
2026-09-017578+3Sato Hub changed the scoring method
2026-07-247975-4the project
2026-07-207579+4Sato Hub changed the scoring method
2026-07-147275+3Sato Hub changed the scoring method
2026-06-256672+6Sato Hub changed the scoring method
2026-06-176566+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 & liveness35/35
35
Code transparency12/20
20
Interface verifiability8/10
10
Docs & demo6/10
10
Listing transparency & provenance14/15
15
Independent verification3/10
10

The observed record

100% 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: answered our check2026-07-15: answered our check2026-07-16: answered our check2026-07-17: answered our check2026-07-18: answered our check2026-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-1378HighActiveup
2026-09-1278HighActiveup
2026-09-1178HighActiveup
2026-09-1078HighActiveup
2026-09-0978HighActiveup
2026-09-0878HighActiveup
2026-09-0778HighActiveup
2026-09-0678HighActiveup
2026-09-0578HighActiveup
2026-09-0478HighActiveup
2026-09-0378HighActiveup
2026-09-0278HighActiveup
2026-09-0178HighActiveup
2026-08-3175HighActiveup
2026-08-3075HighActiveup
2026-08-2975HighActiveup
2026-08-2875HighActiveup
2026-08-2775HighActiveup
2026-08-2675HighActiveup
2026-08-2575HighActiveup
2026-08-2475HighActiveup
2026-08-2375HighActiveup
2026-08-2275HighActiveup
2026-08-2175HighActiveup
2026-08-2075HighActiveup
2026-08-1975HighActiveup
2026-08-1875HighActiveup
2026-08-1775HighActiveup
2026-08-1675HighActiveup
2026-08-1575HighActiveup
2026-08-1475HighActiveup
2026-08-1375HighActiveup
2026-08-1275HighActiveup
2026-08-1175HighActiveup
2026-08-1075HighActiveup
2026-08-0975HighActiveup
2026-08-0875HighActiveup
2026-08-0775HighActiveup
2026-08-0675HighActiveup
2026-08-0575HighActiveup
2026-08-0475HighActiveup
2026-08-0375HighActiveup
2026-08-0275HighActiveup
2026-08-0175HighActiveup
2026-07-3175HighActiveup
2026-07-3075HighActiveup
2026-07-2975HighActiveup
2026-07-2875HighActiveup
2026-07-2775HighActiveup
2026-07-2675HighActiveup
2026-07-2575HighActiveup
2026-07-2475HighActiveup
2026-07-2379HighActiveup
2026-07-2279HighActiveup
2026-07-2179HighActiveup
2026-07-2079HighActiveup
2026-07-1975HighActiveup
2026-07-1875HighActiveup
2026-07-1775HighActiveup
2026-07-1675HighActiveup
2026-07-1575HighActiveup
2026-07-1475HighActiveup
2026-07-1372HighActivenot checked
2026-07-1272HighActivenot checked
2026-07-1172HighActivenot checked
2026-07-1072HighActivenot checked
2026-07-0972HighActivenot checked
2026-07-0872HighActivenot checked
2026-07-0772HighActivenot checked
2026-07-0672HighActivenot checked
2026-07-0572HighActivenot checked
2026-07-0472HighActivenot checked
2026-07-0372HighActivenot checked
2026-07-0272HighActivenot checked
2026-07-0172HighActivenot checked
2026-06-3072HighActivenot checked
2026-06-2772HighActivenot checked
2026-06-2672HighActivenot checked
2026-06-2572HighActivenot checked
2026-06-2466MediumActivenot checked
2026-06-2266MediumActivenot checked
2026-06-2066MediumActivenot checked
2026-06-1966MediumActivenot checked
2026-06-1866MediumActivenot checked
2026-06-1766MediumActivenot checked
2026-06-1665MediumActivenot checked
2026-06-1565MediumActivenot checked
2026-06-1465MediumActivenot checked
2026-06-1365MediumActivenot checked
2026-06-1265MediumActivenot 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 12, 2026
    Edited: chains supported
  2. Sep 7, 2026
    Verified: deploy spec
  3. Jun 25, 2026
    Enriched: supported integrations, deployment options, has pricing, marketplace notes
  4. Jun 25, 2026
    Sato Score tier: Medium → High
    Score 66 → 72.
  5. 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