Skip to main content
Sign in
← avoid.net

Verify a decision

Every moderation decision on AVOID.NET is anchored to the Solana blockchain. You don't have to trust us — you can verify cryptographically that we committed to a verdict at a specific moment and have not rewritten it.

How verification works

  1. We commit. When a moderator accepts/rejects a submission, we serialize the decision into deterministic UTF-8 bytes (payload_canonical_string), hash it with SHA-256, encode the digest as base58, and write it to Solana inside an SPL Memo v2 transaction.
  2. We store the bytes. The exact bytes we hashed are stored alongside the decision in our database. Anyone can read them and recompute the hash in any language.
  3. You compare three values. Database hash, your independently-recomputed hash, and the hash inside the on-chain memo. If all three match, the decision is authentic and timestamped.
The on-chain memo format is AVOID.NET|v1|h:<b58-sha256>|d:<id>|t:<iso>

Find a signature on any investigation page's decision log, or run python -m src.verify_decision --signature <sig> for a CLI check.

Decision
review_revise · Orca
View on Solana ↗
Sequence
#3
Score
85 → 80 (-5)
Cluster
mainnet-beta
Slot
423927848
Off-chain at
2026-06-03T01:32:46.169Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
67CxJ9kVqRiY6PGvayp1J3ATYgVg532QriVXKHLjvuXA
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1431 chars)
{"actor":"judge","decided_at":"2026-06-03T01:32:46.013Z","decision":"review_revise","investigation_id":"06fdfbe1-7e9b-4a4f-8302-97f38657812a","new_score":80,"page_slug":"orca","prev_score":85,"reason":"The review confirmed 28 of 36 claims and found an overall disputed rate of 5.6%, which falls within the approvable range. However, one disputed finding (claim_findings[19]) identifies a material factual error in the Centralization & Upgrade Authority Risk section: the page states the program upgrade authority status 'has not been publicly confirmed' to be governed by a multisig, when current public sources document a 5/9 multisig with a 24-hour timelock. This misstatement is flagged as a high-priority coverage gap and warrants correction before the section accurately characterizes the protocol's controls. Additional minor issues include a Neodyme PDF URL returning 404 (claim_findings[14], link rot on a cited audit source), a Contributor Grants allocation that cannot be confirmed at the stated 5.50% figure versus the documented 5.00% (claim_findings[25]), and a TVL range that appears above current market levels (claim_findings[12]). These issues collectively require targeted revisions but do not undermine the page's overall factual integrity. Reviewer confidence is 0.85.","score_delta":-5,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}