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
20 (-8)
Cluster
mainnet-beta
Slot
443516442
Off-chain at
2026-08-25T19:21:27.748Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
8iNCMdViQwNJkqQVPF8SZrM8VTtJKRE5BEwikWGJTGxr
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1603 chars)
{"actor":"judge","decided_at":"2026-08-25T19:21:27.438Z","decision":"review_revise","investigation_id":"0a172da3-8249-44fd-a8fa-21542a823994","new_score":0,"page_slug":"blazar-token-john-a-desalvo","prev_score":2,"reason":"Using the reviewer's own claim-by-claim findings (17 entries, not the 18 stated in its summary), the disputed-plus-unverifiable rate works out to about 17.6%, placing this page in the minor-issues band. The page's central allegations against John A. DeSalvo -- the Blazar Token scheme mechanics, the $623,888 raised from 222 investors, the May 2022 rug-pull, the March 2024 guilty plea, and the August 2026 SEC settlement terms -- are all independently confirmed against primary sources (claim_findings[0-3, 6, 8-13, 15-16]). Two real defects were found: the page cites SEC Litigation Release LR-25814 for the 2026 settlement when that release is actually the 2023 charging document, and the correct release is LR-26599 (claim_findings[4]); and it places DeSalvo's residence, Linwood, in the wrong county (claim_findings[5]). A third issue -- widening the SEC's precise Brokerage-1 figure of '$95,000 from 17 investors' into an unsupported '$95,000-$100,000 from 17-20 investors' range (claim_findings[7]) -- rounds upward against the defendant without support. None of these errors change the substance of the allegations, and no coverage gap was rated high priority, so the page needs correction rather than removal or a status change.","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}