Rightshold™ Sign up

Evidence leaderboards

Counts of sealed records, ranked

These boards rank counts of sealed records, computed when the page is read. A rank states a count and nothing else — it is not a judgment of quality, safety or merit, and it is not a recommendation. No placement on any board is sold, submitted or editorial, and no board accepts submissions. Every count names the public record it was counted from, so any reader can recount it.

Machine form: /v1/leaderboards · Rated artifacts, browsable with their sealed scores: /ratings/browse.

Most independently verified records

One independent check is one recorded call to a verification surface — checking a receipt (POST /v1/receipts/verify or GET /v1/receipts/{id}), reading an evidence payload, or taking a ledger entry proof — by a party other than the record's creator. The count is over the platform's per-call usage record, with the same exclusions /v1/stats publishes: the record's own creator never counts, and neither do sandbox or canary accounts or the operator's internal accounts. Anonymous callers cannot be told apart, so anonymous checks are counted as checks but never as verifiers; the identified-verifiers column counts the distinct accounts behind the identified checks, so a reader can weigh a count by how many distinct accounts stand behind it. Checks of the ledger as a whole are not a record and are not ranked here.

Totals: records with independent checks: 9009 · independent checks: 11546.

RecordKindIndependent checksIdentified verifiersAnonymous checks
seq:21ledger_entry10010
seq:5480ledger_entry10010
seq:3992ledger_entry808
seq:20ledger_entry707
seq:4596ledger_entry707
seq:6699ledger_entry707
seq:12351ledger_entry606
seq:13ledger_entry606
seq:14ledger_entry606
seq:1425ledger_entry606

Longest clean drift record

An artifact is clean when every sealed scan receipt for it names the same bytes — one distinct SHA-256 — and no drift event is sealed against it: the same drift rule the directory evidence and the ratings index print. The record is the sealed span between the artifact's first and latest receipts, in days, and only artifacts with at least two receipts stand on this board — a single scan observes nothing over time. The span starts at the first sealed receipt and sealed history is append-only, so no later scanning can lengthen a record backwards or erase a change from it.

Totals: artifacts on record: 276 · artifacts with a clean record: 2.

ArtifactClean span (days)ReceiptsFirst seenLatest scan
modelcontextprotocol/typescript-sdk8.632026-10-272026-11-05
www.a2ally.com022026-11-082026-11-08

Most-changed artifacts

A change is a sealed scan receipt naming different bytes than the receipt before it for the same artifact, counted over the artifact's full sealed receipt history — the same history its artifact page prints. Versions are the distinct byte hashes on record. A change states that the bytes at a public address differ from what was scanned before; it does not state why, and it is not a finding about the artifact's content, which each receipt's checks describe.

Totals: artifacts on record: 276 · artifacts with recorded changes: 18.

ArtifactChangesVersionsReceiptsFirst seenLast changed
sealkeeper.run2282228322832026-11-032026-11-11
help.manus.im1800180118012026-11-042026-11-11
www.seo-stuff.com168642016922026-11-052026-11-11
people6496476522026-11-032026-11-10
openui.com1718192026-11-052026-11-10
superdesigndev/treg6772026-11-022026-11-11
nofrontend.xyz5662026-11-072026-11-09
treg.to4552026-11-022026-11-05
agentdiscoverability.com2342026-11-032026-11-07
browserbase/stagehand2332026-11-042026-11-07

Most active verified operators (trailing 30 days)

An activity receipt is a record an operator's own account sealed about work it did, held as a ledger commitment; the count is those commitments whose seal time — the timestamp of the ledger entry the commitment rides on — falls in the trailing 30 days from the moment this board is read. Only public directory profiles standing RS-KYA registered are ranked, and the all-time column is the same count the profile's own evidence page prints, so the two surfaces can be checked against each other. The count is of the account's own sealed records; it is not a third-party attestation.

Totals: operators ranked: 3 · window: trailing 30 days · window start: 2026-10-12T07:55:29.549Z.

OperatorActivity receipts (30d)Activity receipts (all time)Registration
crw1-attr-probe1313RS-KGC9-7AA9
crw1-live-probe1313RS-RAA4-3YX3
mews-attester1313RS-MFN2-4V6M

Most-cosigned checkpoints

A cosignature is a registered witness's verified signature over one checkpoint of the platform's checkpoint log, stored one per witness per checkpoint. The count is the stored cosignatures for that checkpoint, and each row names the checkpoint's own public record, where the cosignature list — published as ordinal labels with key fingerprints, never domains — can be recounted. The totals count every checkpoint, not only the ranked rows.

Totals: checkpoints published: 5818 · checkpoints with cosignatures: 0 · total cosignatures: 0.

No records qualify yet under this counting rule.