Sato Hub
← Raydium verification record

Score history

Raydium

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

95

Change over 90d

+13

Days measured

90

Days missed

4

Sato Score, daily

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

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

DateFromToChangeCause
2026-07-208795+8Sato Hub changed the scoring method
2026-07-149787-10Sato Hub changed the scoring method
2026-06-258297+15Sato 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 transparency19/20
20
Interface verifiability8/10
10
Docs & demo10/10
10
Listing transparency & provenance15/15
15
Independent verification8/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-1395HighActiveup
2026-09-1295HighActiveup
2026-09-1195HighActiveup
2026-09-1095HighActiveup
2026-09-0995HighActiveup
2026-09-0895HighActiveup
2026-09-0795HighActiveup
2026-09-0695HighActiveup
2026-09-0595HighActiveup
2026-09-0495HighActiveup
2026-09-0395HighActiveup
2026-09-0295HighActiveup
2026-09-0195HighActiveup
2026-08-3195HighActiveup
2026-08-3095HighActiveup
2026-08-2995HighActiveup
2026-08-2895HighActiveup
2026-08-2795HighActiveup
2026-08-2695HighActiveup
2026-08-2595HighActiveup
2026-08-2495HighActiveup
2026-08-2395HighActiveup
2026-08-2295HighActiveup
2026-08-2195HighActiveup
2026-08-2095HighActiveup
2026-08-1995HighActiveup
2026-08-1895HighActiveup
2026-08-1795HighActiveup
2026-08-1695HighActiveup
2026-08-1595HighActiveup
2026-08-1495HighActiveup
2026-08-1395HighActiveup
2026-08-1295HighActiveup
2026-08-1195HighActiveup
2026-08-1095HighActiveup
2026-08-0995HighActiveup
2026-08-0895HighActiveup
2026-08-0795HighActiveup
2026-08-0695HighActiveup
2026-08-0595HighActiveup
2026-08-0495HighActiveup
2026-08-0395HighActiveup
2026-08-0295HighActiveup
2026-08-0195HighActiveup
2026-07-3195HighActiveup
2026-07-3095HighActiveup
2026-07-2995HighActiveup
2026-07-2895HighActiveup
2026-07-2795HighActiveup
2026-07-2695HighActiveup
2026-07-2595HighActiveup
2026-07-2495HighActiveup
2026-07-2395HighActiveup
2026-07-2295HighActiveup
2026-07-2195HighActiveup
2026-07-2095HighActiveup
2026-07-1987HighActiveup
2026-07-1887HighActiveup
2026-07-1787HighActiveup
2026-07-1687HighActiveup
2026-07-1587HighActiveup
2026-07-1487HighActiveup
2026-07-1397HighActivenot checked
2026-07-1297HighActivenot checked
2026-07-1197HighActivenot checked
2026-07-1097HighActivenot checked
2026-07-0997HighActivenot checked
2026-07-0897HighActivenot checked
2026-07-0797HighActivenot checked
2026-07-0697HighActivenot checked
2026-07-0597HighActivenot checked
2026-07-0497HighActivenot checked
2026-07-0397HighActivenot checked
2026-07-0297HighActivenot checked
2026-07-0197HighActivenot checked
2026-06-3097HighActivenot checked
2026-06-2797HighActivenot checked
2026-06-2697HighActivenot checked
2026-06-2597HighActivenot checked
2026-06-2482HighActivenot checked
2026-06-2282HighActivenot checked
2026-06-2082HighActivenot checked
2026-06-1982HighActivenot checked
2026-06-1882HighActivenot checked
2026-06-1782HighActivenot checked
2026-06-1682HighActivenot checked
2026-06-1582HighActivenot checked
2026-06-1482HighActivenot checked
2026-06-1382HighActivenot checked
2026-06-1282HighActivenot 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. Jul 21, 2026
    Verified: deploy spec
  2. Jun 25, 2026
    Enriched: has demo, demo url
  3. Jun 25, 2026
    Auto-enriched: creator name, creator profile url, deployment options, supported integrations +1 more
  4. 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