Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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 · DIMO
View on Solana ↗
Sequence
#5
Score
52 → 52 (0)
Cluster
mainnet-beta
Slot
456641897
Off-chain at
2026-10-14T00:36:28.766Z
Anchored at
2026-10-14T00:36:39.096Z
Block time
—

Independent verification

1. Database (off-chain)
HhYfLVnRfpWdUysB1K7VSuhh3ckPf9JWjcXXcfMAJxnQ
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1148 chars)
{"actor":"reviewer","artifact_identity":"edf38bb5091d9a40302c685564fe9df5","decided_at":"2026-10-14T00:36:28.526Z","decision":"review","disputed_pct":0.4444,"findings_hash":"Bo7emWyuZY4CDEYDypM8QV2P6k4Ac1NNiNkAJXgkDx1e","investigation_id":"f3df7ac8-3072-4759-a393-5cd4f1b75f1d","mode":"findings_only","new_score":52,"page_content_hash":"c9240ee205a543e8d7fd16577c8b7bcf62f1b54f2eefe17716bcfac7656b4c63","page_slug":"dimo","prev_score":52,"reason":"The incident core (30M DIMO withdrawn after a proxy upgrade, about $40,000 realized, CertiK alert, reverted upgrade and multisig move) and the Series A details match the sources I could fetch. Problems: the 57% 30-day decline is a trailing figure published the day of the incident but is presented as caused by it, the ZachXBT sentence has no support, and several details (Wormhole, one-hour timing, seed amount) rest on sources I could not confirm. Most sourcing is low-tier aggregators; X primary posts were not retrievable and many sources are unarchived.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}