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 · Poly Network
- Sequence
- #5
- Score
- 37 → 37 (0)
- Cluster
- mainnet-beta
- Slot
- 464265243
- Off-chain at
- 2026-11-01T22:46:57.329Z
- Anchored at
- 2026-11-01T22:47:00.000Z
- Block time
- 2026-11-01T22:47:00.000Z
Independent verification
- 1. Database (off-chain)
- 4VqK72sMujoaw3wCUBsSiwecfJBF7cdd3T22NyCxobSo
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1865 chars)
{"actor":"judge","artifact_identity":"09414f7799041c314f2b3100f1356e92","band_override":null,"decided_at":"2026-11-01T22:46:57.075Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.5,"investigation_id":"97c36ce3-a65c-45b5-9ba7-f3fd0d7701a1","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":37,"page_slug":"poly-network","prev_score":37,"reason":"Of 10 claims checked, 1 was disputed and 3 could not be verified (4 of 10, 40%), which puts the page in the significant-issues band. The core history (the August 2021 exploit and fund return, the July 2023 key compromise, the September 2024 termination) was confirmed or partly supported. The disputed items are the Tether freeze, dated August 15 when it was reported August 10 (claim_findings[0]), and the statement that there were two security incidents, which leaves out a third exploit in August 2024 (claim_findings[5], omission_findings[0]). The page also has an unsourced ZachXBT attribution, an unlocated Dedaub quotation, and internal 'survivor page' and 'merged page' wording that should be removed. The review rested partly on search snippets and secondary sources, so the penalty stops short of a failed factcheck.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":5,"severity_override":{"applied":true,"band":"significant","from_band":"significant","reason":"omission_findings[0] (the August 12, 2024 exploit, about $3-5M, six weeks before the shutdown) is material and the page's 'two major security incidents' wording is disputed by claim_findings[5]. The percentage band is already significant, so the override confirms that band and does not move to deny."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}