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
#5
Score
0 → 0 (0)
Cluster
mainnet-beta
Slot
461977476
Off-chain at
2026-10-27T06:58:05.737Z
Anchored at
2026-10-27T06:58:35.000Z
Block time
2026-10-27T06:58:35.000Z

Independent verification

1. Database (off-chain)
91tfjzy2h9vuJjeem4BEfmc7vki8abCCw77AGx3mKqSu
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1601 chars)
{"actor":"judge","artifact_identity":"92102bb05e38b15c8d8748219c8d4a40","band_override":null,"decided_at":"2026-10-27T06:58:05.347Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3333,"investigation_id":"c27de1ed-c5ed-41e4-8277-1c5fe185f742","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"fundsz-brian-early-and-alisha-ann-kingrey","prev_score":0,"reason":"Of 18 claim findings, 5 were disputed and 1 could not be verified, giving a disputed rate of about 33%. The disputes are two recurring date errors: the complaint was filed July 31, 2023, not August 11, which is the press release date (claim_findings[0], [1]), and the default judgment was entered September 15, 2026, not September 30, which is the CFTC announcement date (claim_findings[2] to [4]). Several further claims were only partly supported: the 14,000 figure is the defendants' own membership claim, the court counted 9,138 participants with losses (claim_findings[5]); 'did not respond' omits that answers were stricken (claim_findings[6], [7]); and the Ponzi label is not in the CFTC complaint (claim_findings[13]). The core facts, amounts, defendants and sanctions are confirmed by CFTC primary documents, and no material omission or status contradiction was reported, so the verdict sits at the low end of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}