Sato Hub
← Brickken verification record

Score history

Brickken

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

29

Change over 57d

+17

Days measured

57

Days missed

0

Sato Score, daily

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

1 change attributable to the project, 2 caused by a revision of the scoring method.

DateFromToChangeCause
2026-09-032529+4the project
2026-09-011325+12Sato Hub changed the scoring method
2026-07-201213+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 & liveness20/35
35
Code transparency0/20
20
Interface verifiability0/10
10
Docs & demo0/10
10
Listing transparency & provenance5/15
15
Independent verification4/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-1329LowActiveup
2026-09-1229LowActiveup
2026-09-1129LowActiveup
2026-09-1029LowActiveup
2026-09-0929LowActiveup
2026-09-0829LowActiveup
2026-09-0729LowActiveup
2026-09-0629LowActiveup
2026-09-0529LowActiveup
2026-09-0429LowActiveup
2026-09-0329LowActiveup
2026-09-0225LowActiveup
2026-09-0125LowActiveup
2026-08-3113LowActiveunknown
2026-08-3013LowActiveunknown
2026-08-2913LowActiveunknown
2026-08-2813LowActiveunknown
2026-08-2713LowActiveunknown
2026-08-2613LowActiveunknown
2026-08-2513LowActiveunknown
2026-08-2413LowActiveunknown
2026-08-2313LowActiveunknown
2026-08-2213LowActiveunknown
2026-08-2113LowActiveunknown
2026-08-2013LowActiveunknown
2026-08-1913LowActiveunknown
2026-08-1813LowActiveunknown
2026-08-1713LowActiveunknown
2026-08-1613LowActiveunknown
2026-08-1513LowActiveunknown
2026-08-1413LowActiveunknown
2026-08-1313LowActiveunknown
2026-08-1213LowActiveunknown
2026-08-1113LowActiveunknown
2026-08-1013LowActiveunknown
2026-08-0913LowActiveunknown
2026-08-0813LowActiveunknown
2026-08-0713LowActiveunknown
2026-08-0613LowActiveunknown
2026-08-0513LowActiveunknown
2026-08-0413LowActiveunknown
2026-08-0313LowActiveunknown
2026-08-0213LowActiveunknown
2026-08-0113LowActiveunknown
2026-07-3113LowActiveunknown
2026-07-3013LowActiveunknown
2026-07-2913LowActiveunknown
2026-07-2813LowActiveunknown
2026-07-2713LowActiveunknown
2026-07-2613LowActiveunknown
2026-07-2513LowActiveunknown
2026-07-2413LowActiveunknown
2026-07-2313LowActiveunknown
2026-07-2213LowActiveunknown
2026-07-2113LowActiveunknown
2026-07-2013LowActiveunknown
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. Jul 21, 2026
    Edited: onchain address
  2. Jul 20, 2026
    Edited: deploy spec
  3. Jul 19, 2026
    Listed on Sato Hub
  4. 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