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 · Mixin Network
View on Solana ↗
Sequence
#3
Score
63 → 63 (0)
Cluster
mainnet-beta
Slot
462182888
Off-chain at
2026-10-27T19:06:27.802Z
Anchored at
2026-10-27T19:06:38.000Z
Block time
2026-10-27T19:06:38.000Z

Independent verification

1. Database (off-chain)
HxHPUKwK5bY8ePoA8GKZrSwWsDsxY1UR1rqhrWiKd7eV
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1402 chars)
{"actor":"reviewer","artifact_identity":"dec8d6e9058c56f9e49231664db7a84e","decided_at":"2026-10-27T19:06:27.681Z","decision":"review","disputed_pct":0.2,"findings_hash":"4TAmztKup9YtWMD6HJVRw5t5VKGuKK1iAYsb5jZLjWad","investigation_id":"e12ac5bb-f642-49d6-8467-1c72ad1d83bb","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":63,"omissions":{"material":0,"total":1},"page_content_hash":"bb41194e517ccbd894ba92db3f70515d6f79f0c76112a9259c44a9ad9c0e7223","page_slug":"mixin-network","prev_score":63,"reason":"The core hack facts (date, ~$200M, asset breakdown, Merkle exploiter data, February 2026 Tornado Cash movement and remaining balances) match the sources I fetched. The main defect is that the October 2025 repayment update is cited to a Bitget article that is actually the February 2024 MDT launch piece and does not contain the claim. The Merkle publication date in the timeline is imprecise (the article is dated September 27). The MDTu September 2026 deadline has passed with no status given. Background and biography claims were largely not checked.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}