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
38 → 26 (-12)
Cluster
mainnet-beta
Slot
462051991
Off-chain at
2026-10-27T11:22:25.022Z
Anchored at
2026-10-27T11:22:39.000Z
Block time
2026-10-27T11:22:39.000Z

Independent verification

1. Database (off-chain)
8BfL1kCQb27FLyKbdH3hLTQsUA1RRSNaCfCCHBveKEYg
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1626 chars)
{"actor":"judge","artifact_identity":"f5aab6c08219f050ae800c4cbe5ecdf8","band_override":null,"blocked_count":3,"decided_at":"2026-10-27T11:22:24.508Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3333,"investigation_id":"68c31745-7e93-46e5-90b3-8250d884cf08","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"page_slug":"world-mobile-token-wmtx-singularitynet-bridge-key-compromise","prev_score":38,"reason":"Of 12 claim findings, 3 were excluded because the sources blocked the reviewer, leaving 9; 2 were disputed (claim_findings[5] and [6], the same 'more than 48 hours' error) and 1 could not be found in the sources (claim_findings[4], the 'committee of one' claim), giving about 33%, which falls in the significant-issues band. The core incident (53.838M WMTx minted, $16.77M attacker cluster, no per-conversion limit, unbound recipient) was confirmed, and the disputed items are one repeated arithmetic error, so the penalty sits at the lenient end of the band. The response and migration narrative rests on a paywalled post and an out-of-date CoinMarketCap archive (coverage gap, high priority), and the reviewer's confidence is moderate (0.5). The page should be corrected, not denied.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-12,"score_limit":{"applied":-12,"limited":true,"proposed":-15,"rule":"limited_no_second_opinion","second":null},"scored_claims":9,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}