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
- 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. - 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.
- 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 · Pons V2 / Robinhood Chain Memecoin Extraction Ring
- Sequence
- #3
- Score
- 4 → 0 (-8)
- Cluster
- mainnet-beta
- Slot
- 461973591
- Off-chain at
- 2026-10-27T06:44:32.735Z
- Anchored at
- 2026-10-27T06:44:50.000Z
- Block time
- 2026-10-27T06:44:50.000Z
Independent verification
- 1. Database (off-chain)
- 9tqz9PUmR1t8ZGLdZLBKSiCF6GaWc3HUtW9v6wKjN5Ph
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1490 chars)
{"actor":"judge","artifact_identity":"7540d8044e7575adb5c999973978bbc6","band_override":null,"decided_at":"2026-10-27T06:44:32.414Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1667,"investigation_id":"ae9f4d90-e94b-4465-aaca-eb9fbd5e2d62","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"pons-v2-robinhood-chain-memecoin-extraction-ring","prev_score":4,"reason":"The core allegations (53 launches, at least $18.43M, Bitquery's 56 launches and $15.5M, GoPlus's figures) are confirmed or substantially supported and are framed as unadjudicated. 2 of 12 claims (16.7%) could not be verified: claim_findings[8] (Pons launch on July 13) and claim_findings[9] (auditor names) were not found in the cited sources. Smaller corrections are also needed: the 82% to 86% supply range applies to nine launches rather than ten (claim_findings[1]), and the cited source for the August 4 Pons V2 go-live is dated August 1 and says V2 had already rolled out (claim_findings[7]). Two archive links point to unrelated pages and should be replaced, and the page's status ends September 29 while The Block's article was updated October 19. No shutdown, sanction or material omission was found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}