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 · Volo Protocol
- Sequence
- #2
- Score
- 47 → 47 (0)
- Cluster
- mainnet-beta
- Slot
- 443525374
- Off-chain at
- 2026-08-27T10:49:45.116Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 35TsUXdsiyvPgfoawZ4uCvn3wdQnGMGtebotLrVNDs26
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (982 chars)
{"actor":"reviewer","decided_at":"2026-08-27T10:49:44.602Z","decision":"review","investigation_id":"0c625ed3-6bc1-4649-a726-569f64e5e919","new_score":47,"page_slug":"volo-protocol","prev_score":47,"reason":"The page's core factual claims about Volo Protocol's product, the NAVI acquisition, audit history, and the mechanics/amounts of the April 2026 exploit are well corroborated by both the page's own cited sources and independent reporting, including outlets not cited by the page. The most material defect is that the page's exploit-aftermath sections describe roughly $3 million as unrecovered and unconfirmed, when independent reporting from within a week of the incident (rekt.news, Phemex) shows approximately 90% of funds were recovered, leaving a net loss near $60,000 -- a substantially less severe outcome than the page conveys.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}