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
- Sequence
- #2
- Score
- 18 → 18 (0)
- Cluster
- mainnet-beta
- Slot
- 443505860
- Off-chain at
- 2026-08-08T03:56:37.441Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- FiCFaBZWqXRjGG31zwPJYsP6bCczDYgmZ9CKMtBRRgAy
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1120 chars)
{"actor":"reviewer","decided_at":"2026-08-08T03:56:37.353Z","decision":"review","investigation_id":"b3ddaae2-0b5a-442b-9961-ca72465cfe7a","new_score":18,"page_slug":"dlmc-token-bnb-chain-flash-loan-exploit","prev_score":18,"reason":"The DLMC investigation is well-sourced for its core factual claims. The two primary news sources (CryptoTimes and Cryip) are live, consistent with each other, and the on-chain data on BscScan independently corroborates the block timestamp, contract existence, and address activity patterns. The main weaknesses are: the CertiK audit claim cannot be verified on CertiK's own platform (Skynet 404); the DLMC website is inaccessible (403), making direct verification of marketing claims depend on search snippets and the archived URL (which could also not be fetched); and the page is time-bounded to June 25, 2026 with no coverage of subsequent developments. No claims were found to be outright disputed or contradicted by other reputable sources.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}