Sato Hub
Hyperliquid Python SDK verification record

Score history

Hyperliquid Python SDK

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

76

Change over 90d

-6

Days measured

90

Days missed

4

Sato Score, daily

2026-06-112026-09-13
02550751002026-07-14: Sato Hub changed the scoring method (80 → 81). 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: 90 (High)2026-06-17: 90 (High)2026-06-18: 90 (High)2026-06-19: 90 (High)2026-06-20: 90 (High)2026-06-22: 90 (High)2026-06-24: 90 (High)2026-06-25: 90 (High)2026-06-26: 90 (High)2026-06-27: 90 (High)2026-06-30: 90 (High)2026-07-01: 90 (High)2026-07-02: 90 (High)2026-07-03: 90 (High)2026-07-04: 90 (High)2026-07-05: 80 (High)2026-07-06: 80 (High)2026-07-07: 80 (High)2026-07-08: 80 (High)2026-07-09: 80 (High)2026-07-10: 80 (High)2026-07-11: 80 (High)2026-07-12: 80 (High)2026-07-13: 80 (High)2026-07-14: 81 (High)2026-07-15: 81 (High)2026-07-16: 81 (High)2026-07-17: 81 (High)2026-07-18: 81 (High)2026-07-19: 81 (High)2026-07-20: 81 (High)2026-07-21: 81 (High)2026-07-22: 81 (High)2026-07-23: 81 (High)2026-07-24: 81 (High)2026-07-25: 81 (High)2026-07-26: 81 (High)2026-07-27: 81 (High)2026-07-28: 81 (High)2026-07-29: 81 (High)2026-07-30: 81 (High)2026-07-31: 81 (High)2026-08-01: 81 (High)2026-08-02: 81 (High)2026-08-03: 81 (High)2026-08-04: 81 (High)2026-08-05: 81 (High)2026-08-06: 81 (High)2026-08-07: 81 (High)2026-08-08: 81 (High)2026-08-09: 81 (High)2026-08-10: 81 (High)2026-08-11: 81 (High)2026-08-12: 81 (High)2026-08-13: 81 (High)2026-08-14: 81 (High)2026-08-15: 81 (High)2026-08-16: 81 (High)2026-08-17: 81 (High)2026-08-18: 81 (High)2026-08-19: 81 (High)2026-08-20: 81 (High)2026-08-21: 81 (High)2026-08-22: 81 (High)2026-08-23: 81 (High)2026-08-24: 81 (High)2026-08-25: 81 (High)2026-08-26: 81 (High)2026-08-27: 81 (High)2026-08-28: 81 (High)2026-08-29: 81 (High)2026-08-30: 81 (High)2026-08-31: 81 (High)2026-09-01: 81 (High)2026-09-02: 81 (High)2026-09-03: 76 (High)2026-09-04: 76 (High)2026-09-05: 76 (High)2026-09-06: 76 (High)2026-09-07: 76 (High)2026-09-08: 76 (High)2026-09-09: 76 (High)2026-09-10: 76 (High)2026-09-11: 76 (High)2026-09-12: 76 (High)2026-09-13: 76 (High)8290762026-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

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

DateFromToChangeCause
2026-09-038176-5the project
2026-07-148081+1Sato Hub changed the scoring method
2026-07-059080-10the project
2026-06-168290+8the project

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 verifiability8/10
10
Docs & demo6/10
10
Listing transparency & provenance14/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-1376HighActiveup
2026-09-1276HighActiveup
2026-09-1176HighActiveup
2026-09-1076HighActiveup
2026-09-0976HighActiveup
2026-09-0876HighActiveup
2026-09-0776HighActiveup
2026-09-0676HighActiveup
2026-09-0576HighActiveup
2026-09-0476HighActiveup
2026-09-0376HighActiveup
2026-09-0281HighActiveup
2026-09-0181HighActiveup
2026-08-3181HighActiveup
2026-08-3081HighActiveup
2026-08-2981HighActiveup
2026-08-2881HighActiveup
2026-08-2781HighActiveup
2026-08-2681HighActiveup
2026-08-2581HighActiveup
2026-08-2481HighActiveup
2026-08-2381HighActiveup
2026-08-2281HighActiveup
2026-08-2181HighActiveup
2026-08-2081HighActiveup
2026-08-1981HighActiveup
2026-08-1881HighActiveup
2026-08-1781HighActiveup
2026-08-1681HighActiveup
2026-08-1581HighActiveup
2026-08-1481HighActiveup
2026-08-1381HighActiveup
2026-08-1281HighActiveup
2026-08-1181HighActiveup
2026-08-1081HighActiveup
2026-08-0981HighActiveup
2026-08-0881HighActiveup
2026-08-0781HighActiveup
2026-08-0681HighActiveup
2026-08-0581HighActiveup
2026-08-0481HighActiveup
2026-08-0381HighActiveup
2026-08-0281HighActiveup
2026-08-0181HighActiveup
2026-07-3181HighActiveup
2026-07-3081HighActiveup
2026-07-2981HighActiveup
2026-07-2881HighActiveup
2026-07-2781HighActiveup
2026-07-2681HighActiveup
2026-07-2581HighActiveup
2026-07-2481HighActiveup
2026-07-2381HighActiveup
2026-07-2281HighActiveup
2026-07-2181HighActiveup
2026-07-2081HighActiveup
2026-07-1981HighActiveup
2026-07-1881HighActiveup
2026-07-1781HighActiveup
2026-07-1681HighActiveup
2026-07-1581HighActiveup
2026-07-1481HighActiveup
2026-07-1380HighActivenot checked
2026-07-1280HighActivenot checked
2026-07-1180HighActivenot checked
2026-07-1080HighActivenot checked
2026-07-0980HighActivenot checked
2026-07-0880HighActivenot checked
2026-07-0780HighActivenot checked
2026-07-0680HighActivenot checked
2026-07-0580HighActivenot checked
2026-07-0490HighActivenot checked
2026-07-0390HighActivenot checked
2026-07-0290HighActivenot checked
2026-07-0190HighActivenot checked
2026-06-3090HighActivenot checked
2026-06-2790HighActivenot checked
2026-06-2690HighActivenot checked
2026-06-2590HighActivenot checked
2026-06-2490HighActivenot checked
2026-06-2290HighActivenot checked
2026-06-2090HighActivenot checked
2026-06-1990HighActivenot checked
2026-06-1890HighActivenot checked
2026-06-1790HighActivenot checked
2026-06-1690HighActivenot checked
2026-06-1582HighActivenot checked
2026-06-1482HighActivenot checked
2026-06-1382HighActivenot checked
2026-06-1282HighActivenot checked
2026-06-11unknownActivenot 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 7, 2026
    Verified: deploy spec
  2. Jun 25, 2026
    Enriched: chains supported, marketplace notes
  3. Jun 25, 2026
    Auto-enriched: deployment options
  4. Jun 16, 2026
    Enriched: creator name, creator profile url, supported integrations
  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.