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 · Revert Lend
- Sequence
- #5
- Score
- 57 → 57 (0)
- Cluster
- mainnet-beta
- Slot
- 457818965
- Off-chain at
- 2026-10-16T23:22:35.356Z
- Anchored at
- 2026-10-16T23:22:54.710Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 4JtFeEnpb6r8GvPuvrKMWyhtsSsgrjdDwmCXjT4Ac1Lt
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1881 chars)
{"actor":"reviewer","artifact_identity":"a9d6ac91b77bfab749bb85590e1a4a6f","decided_at":"2026-10-16T23:22:35.169Z","decision":"review","disputed_pct":0.3889,"findings_hash":"HNJcCfK6m4vtkPTjiYYYrgWjQz2sDF2ecswVW7zwNKyT","investigation_id":"4c26ba16-a016-41ac-894d-717867d71117","mode":"findings_only","new_score":57,"page_content_hash":"e266ba1a504d62e29727747c035e5dc54d4c5c24770528f93b5e4bb6b26ba694","page_slug":"revert-lend","prev_score":57,"reason":"The page's central, highest-stakes claims hold up well: both security incidents (Feb 2023 V3Utils, ~$30k; Jan 2026 Base protocol-logic exploit, ~$50k) are independently corroborated, and the detailed Code4rena audit findings (31 vulnerabilities, 6 high/27 medium, and the H-01 through H-06 descriptions) were verified directly against the live Code4rena report, as was the April 2024 mitigation review and the Immunefi $100k Compoundor bounty. Several secondary details are weaker: the '90% of stolen funds from a single account' claim and the ZachXBT attribution for the 2026 incident could not be corroborated by any source, the Encode Club investor claim is asserted with more confidence than the evidence supports (and is inconsistently hedged relative to Daedalus Angels), the $88,500 Code4rena bounty-pool figure could not be confirmed, and the mid-2026 TVL breakdown is now materially higher than current data. Most consequentially, the page contains an internal date contradiction: the May 2026 timeline entry states Revert Lend 'goes live on Ethereum Mainnet,' while the page's own July 2025 points-program entry and the Protocol Overview section already describe an active Ethereum Mainnet deployment a year earlier. No accepted community submissions were present to review.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}