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 · PolyArb
- Sequence
- #4
- Score
- 26 → 26 (0)
- Cluster
- mainnet-beta
- Slot
- 462056115
- Off-chain at
- 2026-10-27T11:36:43.882Z
- Anchored at
- 2026-10-27T11:37:19.000Z
- Block time
- 2026-10-27T11:37:19.000Z
Independent verification
- 1. Database (off-chain)
- sgF9GfmrFNWeAdKZ8AXUeHciCRr8GXchiFbgcCBbPXi
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1506 chars)
{"actor":"judge","artifact_identity":"ab530d195bcbc73b4c152c660bf48378","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T11:36:43.272Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.25,"investigation_id":"bd06de19-e001-4b28-9227-fdcd75358535","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"page_slug":"polyarb","prev_score":26,"reason":"The central claim, that ZachXBT flagged PolyArb as a wallet-drainer front on May 4, 2026, is confirmed by several independent outlets (claim_findings[0]). Three of the 12 checkable findings (25%) were disputed, all in the PhishDestroy domain section. The polyarb.io registration date is January 10, 2026, not April 8, in both the section and the timeline (claim_findings[1], [2]), and the cited source lists MetaMask and SEAL as 'no match' rather than as blocklisting the domain (claim_findings[3]). One finding was left out of the percentage because the source blocked the reviewer (claim_findings[12]). The two omissions are minor, and nothing indicates a shutdown or sanction. The page also lacks on-chain evidence such as drainer addresses and loss totals, a high-priority gap, so a revision is warranted rather than approval.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":12,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}