Score history

Ionic Protocol

Name: Ionic 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

+24

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-16	42	50	+8	the project
2026-10-10	39	42	+3	Sato Hub changed the scoring method
2026-07-30	27	39	+12	the project
2026-07-29	39	27	-12	the project
2026-07-26	27	39	+12	the project
2026-07-20	26	27	+1	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 & liveness20/35

Code transparency12/20

Interface verifiability8/10

Docs & demo0/10

Listing transparency & provenance7/15

Independent verification3/10

The observed record

100% of 59 daily checks since 2026-09-01 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	50	Medium	Early	up
2026-10-28	50	Medium	Early	up
2026-10-27	50	Medium	Early	up
2026-10-26	50	Medium	Early	up
2026-10-25	50	Medium	Early	up
2026-10-24	50	Medium	Early	up
2026-10-23	50	Medium	Early	up
2026-10-22	50	Medium	Early	up
2026-10-21	50	Medium	Early	up
2026-10-20	50	Medium	Early	up
2026-10-19	50	Medium	Early	up
2026-10-18	50	Medium	Early	up
2026-10-17	50	Medium	Early	up
2026-10-16	50	Medium	Early	up
2026-10-15	42	Medium	Early	up
2026-10-14	42	Medium	Early	up
2026-10-13	42	Medium	Early	up
2026-10-12	42	Medium	Early	up
2026-10-11	42	Medium	Early	up
2026-10-10	42	Medium	Early	up
2026-10-09	39	Low	Early	up
2026-10-08	39	Low	Early	up
2026-10-07	39	Low	Early	up
2026-10-06	39	Low	Early	up
2026-10-05	39	Low	Early	up
2026-10-04	39	Low	Early	up
2026-10-03	39	Low	Early	up
2026-10-02	39	Low	Early	up
2026-10-01	39	Low	Early	up
2026-09-30	39	Low	Early	up
2026-09-29	39	Low	Early	up
2026-09-28	39	Low	Early	up
2026-09-27	39	Low	Early	up
2026-09-26	39	Low	Early	up
2026-09-25	39	Low	Early	up
2026-09-24	39	Low	Early	up
2026-09-23	39	Low	Early	up
2026-09-22	39	Low	Early	up
2026-09-21	39	Low	Early	up
2026-09-20	39	Low	Early	up
2026-09-19	39	Low	Early	up
2026-09-18	39	Low	Early	up
2026-09-17	39	Low	Early	up
2026-09-16	39	Low	Early	up
2026-09-15	39	Low	Early	up
2026-09-14	39	Low	Early	up
2026-09-13	39	Low	Early	up
2026-09-12	39	Low	Early	up
2026-09-11	39	Low	Early	up
2026-09-10	39	Low	Early	up
2026-09-09	39	Low	Early	up
2026-09-08	39	Low	Early	up
2026-09-07	39	Low	Early	up
2026-09-06	39	Low	Early	up
2026-09-05	39	Low	Early	up
2026-09-04	39	Low	Early	up
2026-09-03	39	Low	Early	up
2026-09-02	39	Low	Early	up
2026-09-01	39	Low	Early	up
2026-08-31	39	Low	Early	up
2026-08-30	39	Low	Early	up
2026-08-29	39	Low	Early	up
2026-08-28	39	Low	Early	up
2026-08-27	39	Low	Early	up
2026-08-26	39	Low	Early	up
2026-08-25	39	Low	Early	up
2026-08-24	39	Low	Early	up
2026-08-23	39	Low	Early	up
2026-08-22	39	Low	Early	up
2026-08-21	39	Low	Early	up
2026-08-20	39	Low	Early	up
2026-08-19	39	Low	Early	up
2026-08-18	39	Low	Early	up
2026-08-17	39	Low	Early	up
2026-08-16	39	Low	Early	up
2026-08-15	39	Low	Early	up
2026-08-14	39	Low	Early	up
2026-08-13	39	Low	Early	up
2026-08-12	39	Low	Early	up
2026-08-11	39	Low	Early	up
2026-08-10	39	Low	Early	up
2026-08-09	39	Low	Early	up
2026-08-08	39	Low	Early	up
2026-08-07	39	Low	Early	up
2026-08-06	39	Low	Early	up
2026-08-05	39	Low	Early	up
2026-08-04	39	Low	Early	up
2026-08-03	39	Low	Early	up
2026-08-02	39	Low	Early	up
2026-08-01	39	Low	Early	up
2026-07-31	39	Low	Early	up
2026-07-30	39	Low	Early	up
2026-07-29	27	Low	Early	unknown
2026-07-28	39	Low	Early	up
2026-07-27	39	Low	Early	up
2026-07-26	39	Low	Early	up
2026-07-25	27	Low	Early	unknown
2026-07-24	27	Low	Early	unknown
2026-07-23	27	Low	Early	unknown
2026-07-22	27	Low	Early	unknown
2026-07-21	27	Low	Early	unknown
2026-07-20	27	Low	Early	unknown
2026-07-19	26	Low	Early	unknown

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.

Oct 15, 2026
Verified: deploy spec
Oct 10, 2026
Sato Score tier: Low → Medium
Score 39 → 42.
Sep 26, 2026
Edited: entity class, resource type
Sep 24, 2026
Edited: deploy spec
Aug 1, 2026
Sato Hub began tracking this listing
Jul 21, 2026
Edited: onchain address
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