Verify

Christian Rated records relevant review, vote, eligibility and moderation events in a public hash chain. REVA Digital LLC operates the server. Readers and participating companies can inspect the exported history and reproduce the score arithmetic for a stated log prefix.

Solana anchoring is optional. The live panel below identifies whether it is enabled and whether a confirmed anchor is available. An enabled setting is not itself proof that a transaction was confirmed. This page does not claim a production deployment, an immutable program or a five-minute anchor for every event when those details are not shown.

What a hash chain does

Each event includes a fingerprint of the preceding history. Changing an exported event changes the fingerprints that follow it. A saved copy, a previously recorded prefix hash or a confirmed external anchor gives a verifier something to compare with a later export.

A hash chain controlled only by the server operator is not independent proof that the operator never rewrote the entire history. Its value depends on comparison with a prefix or anchor recorded outside that server. A log also cannot reveal an action that was never recorded.

What an anchor adds

When configured and running, the anchoring job attempts to publish an event count and state hash to Solana on its configured cadence. The defaults are a five-minute interval and a 100-event threshold. Service availability and transaction confirmation affect when an anchor is actually available; an attempt is not a confirmation.

A confirmed anchor commits to a particular log prefix. Recomputing that prefix and comparing its hash can reveal a mismatch. The live panel and /api/anchors show recorded anchor information; check the transaction and its confirmation rather than assuming that a placeholder program or state address is deployed.

What can be checked

Question	What the record supports
Does this exported prefix match a saved copy or confirmed anchor?	Recompute the hash chain for the same event count and compare hashes.
Do the published scores match the stated log prefix?	Replay the scoring version, resource, edition and review track identified with the result.
Which organization proposed or confirmed a moderation action?	Inspect the recorded proposal and decision events, including any operator override.
Did someone judge a review fairly?	The record shows the action and reason; fairness still requires human scrutiny and the appeal process.
Is every voter a distinct real person?	No. Account identity and eligibility metadata are attestations, not proof supplied by the hash chain.
Did every participating company approve a resource or decision?	No. A recorded action identifies the organization that acted, not all companies with access.
Was an independent outside review completed?	Only a specific completed review credit establishes that work; a moderator account or anchor does not.

REVA products follow the same recorded scoring rules, with the ownership safeguards described on Conflicts. A correct hash does not by itself prove that every policy was followed or that a review’s conclusions are correct.

How to check

• /api/votes/export returns public events as JSON lines. Use ?since=<seq> for a tail or ?resource=<slug> for a resource filter.
• /api/anchors returns recorded anchor metadata. An empty result is not a confirmed anchor.
• The verification script recomputes the chain and can compare recorded anchors.
• Resource JSON identifies the selected edition, scoring version, event count and prefix hash used for a score. The independent scorer in cmd/score can replay that public export without database access.

For a complete chain check, use the full export rather than treating a resource-filtered subset as the entire history. Preserve the export and prefix information you compared so a later mismatch can be investigated.

Privacy and the limits of the export

The public event export uses pseudonyms, hashes and selected metadata, rather than review text, account emails or private support messages. Public review text and private service records are separate data. See Privacy for access and disclosure details.

Eligibility and legacy metadata remain attestations by Christian Rated. Operational report and request totals on Transparency use service records; they are not part of the public score-replay claim.

Live status

Use the panel below to inspect the current recorded state and any available confirmed anchor. If a saved prefix, exported history, stated score or confirmed anchor disagrees, contact Support with the event count and comparison details.