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 · Aave
- Sequence
- #3
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 419618020
- Off-chain at
- 2026-05-14T04:51:08.978Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- HNZUJNmmUXwRTRg8j4S8R6ttdAAhRJaZ2D8RYgoJvJFx
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1156 chars)
{"actor":"reviewer","decided_at":"2026-05-14T04:51:08.904Z","decision":"review","investigation_id":"87acc083-7c0c-435d-beef-c1a04c27d81a","new_score":0,"page_slug":"aave","prev_score":0,"reason":"The Aave investigation page is broadly well-sourced and factually accurate across security incident history, regulatory narrative, governance dispute coverage, and the Kelp DAO exploit timeline. One material factual error stands out: the claim that GHO grew to over $3.5 billion in circulation by mid-2025 is directly contradicted by Aave's own official 2025 recap ('nearly $500 million') and independent market data (peak approximately $584M); the stated figure is off by a factor of roughly 6-7x. Secondary issues include conflating the September 2018 ETHLend-to-Aave rebrand with the January 2020 V1 launch, an uncertain Kulechov token purchase amount ($10M vs. the $15M he self-reported), an unverifiable 90%-recovery milestone for late April 2026, and two cited audit PDFs that were inaccessible for verification.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}