A1 ratingsVerify the seal

Verify the seal

Every day the published ratings are hashed in a fixed order, chained to the day before, and carried into the Registry's transparency-log checkpoint (Rule N4.4). A rating that changed quietly would break the chain.

Latest seal · 2026-11-19

Recomputed and matches
Ratings sealed
1313
Ratings hash
eb7aa66bbed7821e8637fe6275c39774283fa4e78ae8880b2c927c0c3e45f68c
Recomputed now
eb7aa66bbed7821e8637fe6275c39774283fa4e78ae8880b2c927c0c3e45f68c
Previous seal
2ed2ec47c38fbae4042d83badf497f0dd20bcb8e814ad04b80501d8d54fdff0f
Seal
d212ae70eaa2a93fc716f9e4fc854484a6d39de447b6107cdb6eb24489056955
In log checkpoint
#1250

ratings_sha256 = sha256 of lines product_id:grade:score:pm ordered by product_id; seal = sha256(prev | A1SEAL1 | day | method | products | ratings_sha256)

Check it yourself

Download the data, or read the published history, sort the day's rows by product id, write each as product_id:grade:score:range on its own line, and take the SHA-256. It should equal the ratings hash above. The seal is SHA-256 of previous seal | A1SEAL1 | day | method | count | ratings hash, and the latest seal is a leaf in the transparency log.