Score history

Crossmint Solana Smart Wallets

Name: Crossmint Solana Smart Wallets — 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

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

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

Date	From	To	Change	Cause
2026-09-01	31	34	+3	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 transparency0/20

Interface verifiability0/10

Docs & demo6/10

Listing transparency & provenance5/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	34	Low	Active	up
2026-10-28	34	Low	Active	up
2026-10-27	34	Low	Active	up
2026-10-26	34	Low	Active	up
2026-10-25	34	Low	Active	up
2026-10-24	34	Low	Active	up
2026-10-23	34	Low	Active	up
2026-10-22	34	Low	Active	up
2026-10-21	34	Low	Active	up
2026-10-20	34	Low	Active	up
2026-10-19	34	Low	Active	up
2026-10-18	34	Low	Active	up
2026-10-17	34	Low	Active	up
2026-10-16	34	Low	Active	up
2026-10-15	34	Low	Active	up
2026-10-14	34	Low	Active	up
2026-10-13	34	Low	Active	up
2026-10-12	34	Low	Active	up
2026-10-11	34	Low	Active	up
2026-10-10	34	Low	Active	up
2026-10-09	34	Low	Active	up
2026-10-08	34	Low	Active	up
2026-10-07	34	Low	Active	up
2026-10-06	34	Low	Active	up
2026-10-05	34	Low	Active	up
2026-10-04	34	Low	Active	up
2026-10-03	34	Low	Active	up
2026-10-02	34	Low	Active	up
2026-10-01	34	Low	Active	up
2026-09-30	34	Low	Active	up
2026-09-29	34	Low	Active	up
2026-09-28	34	Low	Active	up
2026-09-27	34	Low	Active	up
2026-09-26	34	Low	Active	up
2026-09-25	34	Low	Active	up
2026-09-24	34	Low	Active	up
2026-09-23	34	Low	Active	up
2026-09-22	34	Low	Active	up
2026-09-21	34	Low	Active	up
2026-09-20	34	Low	Active	up
2026-09-19	34	Low	Active	up
2026-09-18	34	Low	Active	up
2026-09-17	34	Low	Active	up
2026-09-16	34	Low	Active	up
2026-09-15	34	Low	Active	up
2026-09-14	34	Low	Active	up
2026-09-13	34	Low	Active	up
2026-09-12	34	Low	Active	up
2026-09-11	34	Low	Active	up
2026-09-10	34	Low	Active	up
2026-09-09	34	Low	Active	up
2026-09-08	34	Low	Active	up
2026-09-07	34	Low	Active	up
2026-09-06	34	Low	Active	up
2026-09-05	34	Low	Active	up
2026-09-04	34	Low	Active	up
2026-09-03	34	Low	Active	up
2026-09-02	34	Low	Active	up
2026-09-01	34	Low	Active	up
2026-08-31	31	Low	Active	up
2026-08-30	31	Low	Active	up
2026-08-29	31	Low	Active	up
2026-08-28	31	Low	Active	up
2026-08-27	31	Low	Active	up
2026-08-26	31	Low	Active	up
2026-08-25	31	Low	Active	up
2026-08-24	31	Low	Active	up
2026-08-23	31	Low	Active	up
2026-08-22	31	Low	Active	up
2026-08-21	31	Low	Active	up
2026-08-20	31	Low	Active	up
2026-08-19	31	Low	Active	up
2026-08-18	31	Low	Active	up
2026-08-17	31	Low	Active	up
2026-08-16	31	Low	Active	up
2026-08-15	31	Low	Active	up
2026-08-14	31	Low	Active	up
2026-08-13	31	Low	Active	up
2026-08-12	31	Low	Active	up
2026-08-11	31	Low	Active	up
2026-08-10	31	Low	Active	up
2026-08-09	31	Low	Active	up
2026-08-08	31	Low	Active	up
2026-08-07	31	Low	Active	up
2026-08-06	31	Low	Active	up
2026-08-05	31	Low	Active	up
2026-08-04	31	Low	Active	up
2026-08-03	31	Low	Active	up
2026-08-02	31	Low	Active	up
2026-08-01	31	Low	Active	up
2026-07-31	31	Low	Active	up
2026-07-30	31	Low	Active	up
2026-07-29	31	Low	Active	up
2026-07-28	31	Low	Active	up
2026-07-27	31	Low	Active	up
2026-07-26	31	Low	Active	up
2026-07-25	31	Low	Active	up
2026-07-24	31	Low	Active	up
2026-07-23	31	Low	Active	up
2026-07-22	31	Low	Active	up
2026-07-21	31	Low	Active	up
2026-07-20	31	Low	Active	up
2026-07-19	31	Low	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.

Aug 1, 2026
Sato Hub began tracking this listing
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