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 · Poly Network
- Sequence
- #4
- Score
- 37 → 37 (0)
- Cluster
- mainnet-beta
- Slot
- 464265237
- Off-chain at
- 2026-11-01T22:46:57.143Z
- Anchored at
- 2026-11-01T22:46:59.000Z
- Block time
- 2026-11-01T22:46:59.000Z
Independent verification
- 1. Database (off-chain)
- 7ZsVtRm8Vr4steLxBSzaAjwTydBrX82hFyNoD4vKD1sj
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1526 chars)
{"actor":"reviewer","artifact_identity":"09414f7799041c314f2b3100f1356e92","decided_at":"2026-11-01T22:46:57.075Z","decision":"review","disputed_pct":0.5,"findings_hash":"4GRam1Cesu5PaVGqoRugdraRNvz38rJoDNquWFHA2vVc","investigation_id":"97c36ce3-a65c-45b5-9ba7-f3fd0d7701a1","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":37,"omissions":{"material":1,"total":1},"page_content_hash":"d3fc980b9ea7956c38853410db534dfa66f64365b4dd9f3cc8d21b638f4eb8b5","page_slug":"poly-network","prev_score":37,"reason":"The core history (2021 hack and return of funds, July 2023 key compromise, September 2024 termination) is broadly supported by what I checked. Errors and gaps: the Tether freeze is dated August 15 when it was reported August 10 and the funds were later released; one Dedaub quotation could not be found and the Dedaub conclusion is more hedged than the page states; the page omits an August 2024 exploit (about $3-5M) and so wrongly counts two incidents; and one claim about ZachXBT is unsourced. Several sections contain internal merge language that is not suitable for publication. Many cited pages were not individually fetched, and the primary shutdown notice returned 403.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"subject_status":"shut_down","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}