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 · PolyArb
- Sequence
- #3
- Score
- 26 → 26 (0)
- Cluster
- mainnet-beta
- Slot
- 462056109
- Off-chain at
- 2026-10-27T11:36:43.708Z
- Anchored at
- 2026-10-27T11:37:18.000Z
- Block time
- 2026-10-27T11:37:18.000Z
Independent verification
- 1. Database (off-chain)
- HpTVsTQVgUbqXi3gYzCSY9vAUop89vF3BufjADKPCrur
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1434 chars)
{"actor":"reviewer","artifact_identity":"ab530d195bcbc73b4c152c660bf48378","blocked_count":1,"decided_at":"2026-10-27T11:36:43.272Z","decision":"review","disputed_pct":0.25,"findings_hash":"HhFZFLJ3zzqeXA7zcTdKV9ytEKG9zNeHX5y186anfYp2","investigation_id":"bd06de19-e001-4b28-9227-fdcd75358535","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"omissions":{"material":0,"total":2},"page_content_hash":"e1e2ad6a2fa2456b04dceb558630eb626f44d291a3b171e9e663b687d4355708","page_slug":"polyarb","prev_score":26,"reason":"The core allegation (ZachXBT flagged PolyArb as a wallet-drainer front on 2026-05-04) is well corroborated and appropriately hedged. Errors lie in the PhishDestroy section: the polyarb.io registration date is January 10, 2026 and not April 8 (also wrong in the timeline), the MetaMask/SEAL blocklist claim is contradicted by the source's structured data, and the Jupiter impersonation is only an automated label. The Cloudflare pop-up and 25usdc details in the broader-context section were not found in the BingX source. No shutdown or sanctions found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":12,"sequence_num":3,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}