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
40 (-12)
Cluster
mainnet-beta
Slot
443522176
Off-chain at
2026-08-26T22:07:01.417Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
2ZKx8r6mZbv5vnqGkY3TsqrF5ggXjgvgukveAnRPVsNr
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2213 chars)
{"actor":"judge","decided_at":"2026-08-26T22:07:00.953Z","decision":"review_revise","investigation_id":"c19cb8ca-dd3d-45ae-b300-fa683a4915e4","new_score":0,"page_slug":"alex-larson-schultz-overhere-limited-hawk-memecoin","prev_score":4,"reason":"This page's disputed_pct is 20% (5 disputed + 3 unverifiable of 40 claims), squarely in the 10-30% band, and most of the page's factual scaffolding checks out against primary sources, including a complaint the reviewer fetched directly. Two findings carry more weight than their single-claim count suggests: the page cites the Securities Exchange Act of 1934 as the basis for the lawsuit (claim_findings[23]) when the complaint's sole cause of action is under Sections 5 and 12(a)(1) of the Securities Act of 1933 -- a real error about the legal exposure of a named, unconvicted individual, though it appears in two places on the page (a section body and a timeline entry), not four; neither the summary nor the section heading actually names a statute. Separately, a quote attributed to 'reporting by Mashable ... cited in the class action complaint' (claim_findings[6]) does not appear in the complaint at all -- per Bloomberg Law it is co-defendant OverHere's own statement shifting blame onto Schultz, so the page currently dresses up one defendant's unproven accusation as a complaint finding. The page also contradicts its own cited complaint twice by saying Clinton So's statements 'have not been widely reported' (claim_findings[36], [37]), when that complaint quotes him at length. A valuation-vs-amount-raised conflation (claim_findings[34]) and an internally inconsistent lede collapse statistic combining unreconciled source figures (claim_findings[0]) further erode confidence in the page's numeric precision, though neither rises to 'disputed' on its own. Given a moderate reviewer confidence (0.72) and a page that is mostly accurate but has two errors bearing directly on named individuals' legal exposure and evidentiary attribution, a mid-band revision penalty is warranted rather than denial or approval.","score_delta":-12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}