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.

Sequence
#3
Score
18 → 0 (-18)
Cluster
mainnet-beta
Slot
462172159
Off-chain at
2026-10-27T18:28:16.358Z
Anchored at
2026-10-27T18:28:42.000Z
Block time
2026-10-27T18:28:42.000Z

Independent verification

1. Database (off-chain)
3XTZDNHm9ZktHasZT21N4fzkBVry1fQADFjdVHTemL2i
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1385 chars)
{"actor":"judge","artifact_identity":"0617ac1c9a3b9e1c9780dd0e0ba2e00a","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T18:28:16.116Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4615,"investigation_id":"18c96289-1f9d-428f-a5c8-b1865010e775","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"fetch-ai-nunet-cross-project-exploit-september-2026","prev_score":18,"reason":"Of 14 claim findings, one (the attacker address, claim_findings[13]) could not be checked because the source blocked the reviewer, so it is left out. Of the remaining 13, 3 were disputed and 3 could not be verified, giving about 46%, which falls in the significant-issues band. The disputed items are the September 20 attack date (claim_findings[0]) and the statement that all proceeds were converted to ETH (claim_findings[2], [3]); sources point to September 19 and a partial conversion. The core figures (8.72M FET, 408.5M NTX) were confirmed, the subject status matches the page, and the omissions are minor, so the penalty sits at the lower end of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-18,"scored_claims":13,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}