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.

Sequence
#3
Score
2 → 2 (0)
Cluster
mainnet-beta
Slot
443517031
Off-chain at
2026-08-25T19:47:40.235Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
26ucJyyrkDvWBkXrKHgY9mUzD2UJputCEyBPTq1pTZqR
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1877 chars)
{"actor":"judge","decided_at":"2026-08-25T19:47:39.972Z","decision":"review_approve","investigation_id":"3a3b1d11-7205-4579-a9bc-9299fa917a15","new_score":2,"page_slug":"bandcampro-ai-assisted-fraud-campaign","prev_score":2,"reason":"Of 35 claims checked, 29 were confirmed and none were disputed. Applying the disputed_pct formula (disputed + unverifiable) / total, the figure is 2/35 = 5.7%, well inside the 0-10% approve band. The two unverifiable items are exact calendar dates in the timeline (claim_findings[32], claim_findings[33]) that the reviewer could not pin to a source but whose underlying facts were independently confirmed elsewhere. The four partially-supported items (claim_findings[4], [21], [28], [34]) are all minor date-precision or attribution slips -- a placeholder channel-founding date off by about five weeks, a report-publication date off by one day, and one citation crediting a technical detail to The Register that could not be independently confirmed -- none of which touch the page's core allegations. The reviewer found no link rot and no stale citations, and confirmed that the page's central 'AI-assisted' framing tracks Trend Micro's own language. The page does have an open coverage gap -- it never clarifies that the legitimate music platform Bandcamp is unrelated to the threat actor's handle 'bandcampro' -- but the reviewer rated that gap medium, not high priority, and the approve criteria treat coverage gaps as grounds for expansion, not denial, unless marked high priority. There is no mechanism in the decision rules to escalate the verdict on the strength of a medium-priority gap alone, so it does not move this page out of the approve band; it is flagged below for editorial follow-up.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}