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 · AFI Protocol
View on Solana ↗
Sequence
#3
Score
5237 (-15)
Cluster
mainnet-beta
Slot
443525177
Off-chain at
2026-08-27T10:26:15.124Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
HqdDeEjXvcvaqSTqpyNPspR6DwLxHWMoKxx4KxkGLX2J
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1851 chars)
{"actor":"judge","decided_at":"2026-08-27T10:26:14.670Z","decision":"review_revise","investigation_id":"d8ae137c-0798-405d-93fa-cbfb6f83f80e","new_score":37,"page_slug":"afi-protocol","prev_score":52,"reason":"Independent computation from claim_findings confirms the reviewer's own summary: 3 disputed and 2 unverifiable out of 33 claims yields a disputed_pct of 15.15%, placing this page in the 10-30% band, which calls for review_revise with no change to publication status. Within that band, two findings push the penalty toward the top of the allowed range. First, claim_findings[12] and claim_findings[26] show the page asserting AFI's December 2025 vault launch was backed by '$700 million in verified RWA reserves' in two separate sections, while the page's own timeline entry for the same event states $80 million — a figure corroborated by two independent outside sources. This is a self-contradiction on the exact number a reader would use to judge whether the product is adequately backed. Second, claim_findings[21] disputes the page's claim that AFI 'does not publicly identify its founding team,' noting that Chaos Labs, a named and established risk-management firm, publicly identifies itself as AFI's creator; the page omits this and treats an unfounded opacity concern as a red flag. Both issues are also logged as high-priority coverage gaps. Everything else on the page holds up well: the $480K afiUSD exploit narrative (claim_findings[3]-[10]) is corroborated across two outlets, two audit dates were checked against source and confirmed genuine rather than placeholders, and the two unverifiable findings stem from a source behind a bot-check wall rather than any identified inaccuracy.","score_delta":-15,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}