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 · MangoFarmSOL
- Sequence
- #4
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 464377204
- Off-chain at
- 2026-11-02T05:26:18.815Z
- Anchored at
- 2026-11-02T05:26:48.000Z
- Block time
- 2026-11-02T05:26:48.000Z
Independent verification
- 1. Database (off-chain)
- 7TuDvwVBkgXbLGhH9oUU5mFKsPYqcRufHbcUzgh46Mwq
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1569 chars)
{"actor":"judge","artifact_identity":"2622a93962e10d42ea13a9400f5611ee","band_override":null,"decided_at":"2026-11-02T05:26:18.610Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3,"investigation_id":"62f7aab4-ebb9-4d15-9bc0-0739d5b23f3a","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"mangofarmsol","prev_score":0,"reason":"The core facts of the page (13,512 SOL withdrawn, about $1.32M total losses, the laundering route, the 0xfoobar warning and the BananaMiner denial) were confirmed against CertiK and other sources. Three of ten claims could not be verified (30%): the ZachXBT flag (claim_findings[6]) has no support in any readable source, the 'widely cited in the security community' statement (claim_findings[7]) has no source, and the 'as of May 2026' no-action statement (claim_findings[9]) is cited to a February 2024 post, although a web search found nothing contradicting it. The Telegram subscriber count is also unconfirmed (claim_findings[5]), one archive link points to the wrong page, and the page does not mention a $2M loss estimate reported by some outlets. Because the unsupported items are secondary to the core allegation and the page's account of the shutdown is accurate, the penalty sits at the lower end of the revise range.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}