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_revise · DoinGud
View on Solana ↗
Sequence
#3
Score
22 → 2 (-20)
Cluster
mainnet-beta
Slot
462180196
Off-chain at
2026-10-27T18:56:59.023Z
Anchored at
2026-10-27T18:57:06.000Z
Block time
2026-10-27T18:57:06.000Z

Independent verification

1. Database (off-chain)
8Tpk5jDTe63Av9sFCzZaSSaZKbWQptYsr4KpDC6mS8Ja
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1526 chars)
{"actor":"judge","artifact_identity":"cb0f3651303138f3819463aa92afad02","band_override":null,"blocked_count":2,"decided_at":"2026-10-27T18:56:58.790Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3333,"investigation_id":"1f6691f1-c228-4ea1-9e75-37f0d1944f7b","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":2,"page_slug":"doingud","prev_score":22,"reason":"Of 6 scored claims, 2 (33%) could not be verified: the September 21, 2026 exploit in sections[2] and its timeline entry (claim_findings[0] and [1]) both cite only the SlowMist tracker homepage, which showed no DoinGud entry, and searches found nothing. This is the page's headline allegation and the basis of its summary and two high-severity sections, so it weighs heavily. Two claims were blocked by 403 errors (seed round, Cleo acquisition) and were not counted. The reviewer's confidence was low (0.45), nothing was contradicted, and no omissions were found, so the penalty sits in the lower half of the significant band and the page is not denied. The founder and fee-split details are only partly supported by the cited source (claim_findings[6]), and high-priority gaps remain for a specific exploit citation and on-chain transaction hashes.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-20,"scored_claims":6,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}