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_revise · Kevin Rose
- Sequence
- #3
- Score
- 62 → 57 (-5)
- Cluster
- mainnet-beta
- Slot
- 425010321
- Off-chain at
- 2026-06-08T01:21:42.236Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- A4Hk5ymfkuShrQ4AqL1qikf5yPJ3Qr6u5hQwTi7G5mGk
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1320 chars)
{"actor":"judge","decided_at":"2026-06-08T01:21:41.998Z","decision":"review_revise","investigation_id":"16e7e463-92f3-4c98-9433-0cba30367a40","new_score":57,"page_slug":"kevin-rose","prev_score":62,"reason":"The review found no directly disputed claims and a disputed_pct of 7.7%, which would ordinarily support approval. However, three structural issues prevent a clean pass: claim_findings[8] (the 'all-stock deal' characterization of the Yuga acquisition) is unverifiable because Yuga Labs did not disclose deal terms, the primary cited source is dead; two primary cited sources at nftmetria.com return HTTP 404 (link rot flagged in claim_findings[0] and claim_findings[3]); and a high-priority coverage gap identifies that all section content fields are empty, meaning the page consists only of section headings and source lists with no written body text. The core incident claims — the January 2023 phishing attack, stolen NFT details, and Seaport exploit — are well-supported by Tier 1 sources (CoinDesk, Decrypt, Axios). Revisions should replace the dead nftmetria links, remove or qualify the unverified 'all-stock' deal language, and populate the empty section bodies.","score_delta":-5,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}