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
- Sequence
- #2
- Score
- 62 → 62 (0)
- Cluster
- mainnet-beta
- Slot
- 425420165
- Off-chain at
- 2026-06-09T22:40:16.359Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 21gePPcmsb1assiJu68MMjjZH3F7VtPopHFge3eLLZ4J
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1165 chars)
{"actor":"reviewer","decided_at":"2026-06-09T22:40:16.237Z","decision":"review","investigation_id":"e198003e-9540-4950-a4cc-3868bcd92ce3","new_score":62,"page_slug":"gnosis-pay-zodiac-delay-module-exploit","prev_score":62,"reason":"The investigation page is broadly accurate and well-sourced for a fast-moving June 2026 incident. Core claims — exploit date, module versions, loss figure, affected Safe count, on-chain fund movement, Köppelmann reimbursement pledge, and service restoration — are all independently confirmed. The two 'link_rot' verdicts reflect HTTP 403 access restrictions (The Block, The Defiant) rather than true dead links; the underlying claims are confirmed by other sources. One secondary wallet address remains unverifiable from accessible sources. A material coverage gap exists: the page does not mention that the vulnerability was silently patched in the zodiac-core repository on February 27, 2026, months before the exploit, while production instances remained on the vulnerable legacy package.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}