Score history

Self Protocol

Name: Self Protocol — Sato Score daily history
Creator: Sato Hub
License: https://creativecommons.org/licenses/by/4.0/

One dated Sato Score reading per day. Days we changed the scoring method are marked. Not a safety or returns grade.

Score today

Change over 103d

+39

Days measured

103

Days missed

Sato Score, daily

2026-07-19 → 2026-10-29

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

4 changes attributable to the project, 2 caused by a revision of the scoring method.

Date	From	To	Change	Cause
2026-10-19	70	80	+10	the project
2026-10-16	80	70	-10	the project
2026-09-01	77	80	+3	Sato Hub changed the scoring method
2026-08-08	69	77	+8	the project
2026-07-21	50	69	+19	the project
2026-07-20	41	50	+9	Sato 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

Code transparency20/20

Interface verifiability8/10

Docs & demo6/10

Listing transparency & provenance8/15

Independent verification3/10

The observed record

100% of 103 daily checks since 2026-07-19 succeeded. This is the share of OUR checks that succeeded. It is not uptime: a failed check can be on our side. When a check before 2026-09-01 failed, the checks before that date are left out of the rate: the probe counted a bot-block as a failure then and recorded no reason for any failure.

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.

Date	Score	Tier	Status	Our check
2026-10-29	80	High	Active	up
2026-10-28	80	High	Active	up
2026-10-27	80	High	Active	up
2026-10-26	80	High	Active	up
2026-10-25	80	High	Active	up
2026-10-24	80	High	Active	up
2026-10-23	80	High	Active	up
2026-10-22	80	High	Active	up
2026-10-21	80	High	Active	up
2026-10-20	80	High	Active	up
2026-10-19	80	High	Active	up
2026-10-18	70	High	Active	up
2026-10-17	70	High	Active	up
2026-10-16	70	High	Active	up
2026-10-15	80	High	Active	up
2026-10-14	80	High	Active	up
2026-10-13	80	High	Active	up
2026-10-12	80	High	Active	up
2026-10-11	80	High	Active	up
2026-10-10	80	High	Active	up
2026-10-09	80	High	Active	up
2026-10-08	80	High	Active	up
2026-10-07	80	High	Active	up
2026-10-06	80	High	Active	up
2026-10-05	80	High	Active	up
2026-10-04	80	High	Active	up
2026-10-03	80	High	Active	up
2026-10-02	80	High	Active	up
2026-10-01	80	High	Active	up
2026-09-30	80	High	Active	up
2026-09-29	80	High	Active	up
2026-09-28	80	High	Active	up
2026-09-27	80	High	Active	up
2026-09-26	80	High	Active	up
2026-09-25	80	High	Active	up
2026-09-24	80	High	Active	up
2026-09-23	80	High	Active	up
2026-09-22	80	High	Active	up
2026-09-21	80	High	Active	up
2026-09-20	80	High	Active	up
2026-09-19	80	High	Active	up
2026-09-18	80	High	Active	up
2026-09-17	80	High	Active	up
2026-09-16	80	High	Active	up
2026-09-15	80	High	Active	up
2026-09-14	80	High	Active	up
2026-09-13	80	High	Active	up
2026-09-12	80	High	Active	up
2026-09-11	80	High	Active	up
2026-09-10	80	High	Active	up
2026-09-09	80	High	Active	up
2026-09-08	80	High	Active	up
2026-09-07	80	High	Active	up
2026-09-06	80	High	Active	up
2026-09-05	80	High	Active	up
2026-09-04	80	High	Active	up
2026-09-03	80	High	Active	up
2026-09-02	80	High	Active	up
2026-09-01	80	High	Active	up
2026-08-31	77	High	Active	up
2026-08-30	77	High	Active	up
2026-08-29	77	High	Active	up
2026-08-28	77	High	Active	up
2026-08-27	77	High	Active	up
2026-08-26	77	High	Active	up
2026-08-25	77	High	Active	up
2026-08-24	77	High	Active	up
2026-08-23	77	High	Active	up
2026-08-22	77	High	Active	up
2026-08-21	77	High	Active	up
2026-08-20	77	High	Active	up
2026-08-19	77	High	Active	up
2026-08-18	77	High	Active	up
2026-08-17	77	High	Active	up
2026-08-16	77	High	Active	up
2026-08-15	77	High	Active	up
2026-08-14	77	High	Active	up
2026-08-13	77	High	Active	up
2026-08-12	77	High	Active	up
2026-08-11	77	High	Active	up
2026-08-10	77	High	Active	up
2026-08-09	77	High	Active	up
2026-08-08	77	High	Active	up
2026-08-07	69	Medium	Active	up
2026-08-06	69	Medium	Active	up
2026-08-05	69	Medium	Active	up
2026-08-04	69	Medium	Active	up
2026-08-03	69	Medium	Active	up
2026-08-02	69	Medium	Active	up
2026-08-01	69	Medium	Active	up
2026-07-31	69	Medium	Active	up
2026-07-30	69	Medium	Active	up
2026-07-29	69	Medium	Active	up
2026-07-28	69	Medium	Active	up
2026-07-27	69	Medium	Active	up
2026-07-26	69	Medium	Active	up
2026-07-25	69	Medium	Active	up
2026-07-24	69	Medium	Active	up
2026-07-23	69	Medium	Active	up
2026-07-22	69	Medium	Active	up
2026-07-21	69	Medium	Active	up
2026-07-20	50	Medium	Active	up
2026-07-19	41	Medium	Active	up

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.

Sep 26, 2026
Edited: entity class, resource type
Sep 21, 2026
Verified: deploy spec
Aug 8, 2026
Auto-enriched: docs url
Aug 8, 2026
Sato Score tier: Medium → High
Score 69 → 77.
Aug 1, 2026
Sato Hub began tracking this listing
Jul 19, 2026
Edited: chains supported
Jul 19, 2026
Listed on Sato Hub

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 record This week’s movers Dispute this score