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.
- Sequence
- #2
- Score
- 35 → 35 (0)
- Cluster
- mainnet-beta
- Slot
- 462054583
- Off-chain at
- 2026-10-27T11:31:44.506Z
- Anchored at
- 2026-10-27T11:31:53.000Z
- Block time
- 2026-10-27T11:31:53.000Z
Independent verification
- 1. Database (off-chain)
- DPsRARSH9uZJqcdWAtcUcd2DCtou7KCY5bM1yk8DAkYL
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1408 chars)
{"actor":"reviewer","artifact_identity":"c53b5bdde8202fdca4e32eaf3e9a64dd","blocked_count":1,"decided_at":"2026-10-27T11:31:44.104Z","decision":"review","disputed_pct":0,"findings_hash":"Dt6BrhLRv129hh5Qzst23M3qAdb8FTtq6YXTM7VzgdKP","investigation_id":"02ccd163-e530-4447-b984-8da8fb7e1fd5","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":35,"omissions":{"material":0,"total":1},"page_content_hash":"27a3f83d7ddd919e29adde5015fb1ee58ad4b4e82e05fa5d3ddb12c8f791ad20","page_slug":"makerdao-legacy-auction-keeper-exploit-october-2026","prev_score":35,"reason":"The core facts (200 ETH, about $543K, Oct 6 2026, selector 0x8804d1de, auctions 1457-1460, missing access check, nope never called, Tornado funding and laundering) match CertiK and Protos. Problems are an editorial artifact ('The requester's description') in the Tornado Cash section, an unresolved batch-count discrepancy, and the Crypto Times claims, which I could not check because the site returned 403. No contradictions with current sources, and no later developments were found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":10,"sequence_num":2,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}