Skip to main content
AVOID.NET
← 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 · Meteora
View on Solana ↗
Sequence
#10
Score
26 → 26 (0)
Cluster
mainnet-beta
Slot
464296689
Off-chain at
2026-11-02T00:39:08.472Z
Anchored at
2026-11-02T00:39:12.000Z
Block time
2026-11-02T00:39:12.000Z

Independent verification

1. Database (off-chain)
B1F5VYMXwCGU9LscE3PdtXb3RaMuaCE2hzkgGbTMdMug
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2129 chars)
{"actor":"judge","artifact_identity":"cb4d28d682c941032638cdc899ffbd56","band_override":null,"blocked_count":1,"decided_at":"2026-11-02T00:39:08.210Z","decision":"review_revise","delist_requested":false,"disputed_pct":0,"investigation_id":"360a1cab-ff88-4ddb-9d93-11d65e802438","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"page_slug":"meteora","prev_score":26,"reason":"Every checked litigation fact held up, including the Sept 29, 2026 with-prejudice dismissal, the Clarke/Vogt voluntary dismissal dates and Chow's resignation, so the claim-level dispute rate is 0%. The page does leave out the outcome of the ZachXBT insider-trading report, which was published February 26, 2026 and named Axiom rather than Meteora (claim_findings[3], claim_findings[5], omission_findings[0]). Because this omission could mislead readers about Meteora's standing, the page is rated one band above what the percentage alone implies and should be revised with the suggested correction. One finding (claim_findings[7], the Sept 30 judgment text) could not be checked because the court PDF was unreadable, which is a coverage limit rather than a defect of the page.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":7,"sequence_num":10,"severity_override":{"applied":true,"band":"minor","from_band":"approve","reason":"Computed disputed_pct is 0% (7 countable findings, none disputed or unverifiable; one source_blocked finding excluded). However omission_findings[0] is material: the page presents the ZachXBT probe and Meteora's Polymarket odds without saying the Feb 26, 2026 report named Axiom, not Meteora, which could leave readers thinking Meteora is still under suspicion. Escalated to the minor band only, because it is a single defect group (claim_findings[3] and [5], both stale), the page's earlier statements were accurate as of their dates, and no shutdown, exploit or sanction contradicts the page."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}