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
- 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. - 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.
- 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 · AFI Protocol
- Sequence
- #5
- Score
- 61 → 61 (0)
- Cluster
- mainnet-beta
- Slot
- 457590386
- Off-chain at
- 2026-10-16T09:38:45.879Z
- Anchored at
- 2026-10-16T09:39:06.659Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- sNgEU9jevaSyWpp5AWgqcgB3FCifDUbTTsDEqh21b3Z
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1711 chars)
{"actor":"reviewer","artifact_identity":"7892b766c53b7df8ed8ff7ad4949ec59","decided_at":"2026-10-16T09:38:45.584Z","decision":"review","disputed_pct":0.2273,"findings_hash":"AMdmJUSd5vDQKLxczoGzGPQibFMv4iZsqumhw9TMLkN","investigation_id":"d8ae137c-0798-405d-93fa-cbfb6f83f80e","mode":"findings_only","new_score":61,"page_content_hash":"f83acf2cc080f2bc83b653c26bdd0b14edcd2431215d3976244e03084d3daf73","page_slug":"afi-protocol","prev_score":61,"reason":"The core incident reporting (the May 30, 2026 $480K afiUSD exploit, the DAI-to-ETH conversion, the Tornado Cash routing, the firms engaged, and the TVL-unaffected claim) is well-supported by the two cited news articles and corroborated by independent checks. The audit history and bug-bounty details check out cleanly against AFI's own documentation. The most significant problem is a recurring, unsupported $700 million reserves figure that appears in two sections tied to the December 2025 $20M Multipli vault launch — the actual cited launch article, and the page's own timeline entry for the same event, both say $80 million; the $700M figure appears to be an undated, protocol-wide attestation figure from a third-party dapp listing that was misapplied to a specific historical event. This is an internal inconsistency the page should resolve. Secondary findings include an unconfirmed subset of listed ecosystem partners, several vault-level figures (TVL/minting cap, APY range) that could not be verified from the pages reached, and a possible (but unresolved) URL-casing issue on the DefiLlama source link.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}