Skip to main content
Sign in
← 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 · Aave V3
View on Solana ↗
Sequence
#3
Score
6858 (-10)
Cluster
mainnet-beta
Slot
424161627
Off-chain at
2026-06-04T03:24:23.810Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
ANLx5dR5UGK4zxV7eUDbMQKL5iRxXRYxJNFArEoMhCcD
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1362 chars)
{"actor":"judge","decided_at":"2026-06-04T03:24:23.544Z","decision":"review_revise","investigation_id":"96c6369e-4f55-49a7-8101-2c6d114057e2","new_score":58,"page_slug":"aave-v3","prev_score":68,"reason":"The reviewer confirmed 13 of 20 claims outright with strong tier-1 sourcing. The disputed_pct of 15% places this page in the revise band. The single hard-disputed finding (claim_findings[12]: Umbrella launch date stated as June 1, confirmed as June 5 by multiple independent sources) is a minor date error. More consequentially, the $327 million DeFi United fundraise total — stated in both the summary and claim_findings[17] — is not corroborated by any source; credible reporting consistently cites $300M-$320M, making this a repeated overstatement of a headline recovery figure. The AAVE token decline in claim_findings[12] is also understated at 10-13% when primary sources report 16-20%, which affects readers' assessment of market impact severity. Additionally, all seven section content fields are empty (coverage_gaps, priority: high), meaning the page has no body text beyond the summary and timeline — a structural deficiency requiring revision before the page can stand alone as a useful investigation.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}