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 · LeadBlock's Morpho Blue Market
- Sequence
- #2
- Score
- 48 → 48 (0)
- Cluster
- mainnet-beta
- Slot
- 423927827
- Off-chain at
- 2026-06-03T01:32:44.771Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- DaQicAwCzSEa8taX6CRR4GzWsAXyydjyJ5zszYrnYZGk
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1167 chars)
{"actor":"reviewer","decided_at":"2026-06-03T01:32:44.689Z","decision":"review","investigation_id":"0d100113-16a1-4e26-89b0-e41049bbd95e","new_score":48,"page_slug":"leadblocks-morpho-blue-market","prev_score":48,"reason":"The core facts of the October 13, 2024 oracle misconfiguration exploit — amounts, attacker address, SCALE_FACTOR root cause, and Morpho's response — are well-supported by multiple independent sources. The most significant accuracy issues are: (1) the page presents LeadBlock's contested repayment claim as uncontested fact despite community-level on-chain dispute evidence; (2) the risk warnings introduction is framed as a post-incident response when it preceded the incident by five months; and (3) the post-mortem publication date claim for QuillAudits and SolidityScan is inaccurate — only Verichains published on October 18. No claims were found to directly contradict a more credible primary source, but several involve material omissions or mischaracterizations that affect the page's narrative.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}