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 · Hypurr NFTs
- Sequence
- #4
- Score
- 74 → 74 (0)
- Cluster
- mainnet-beta
- Slot
- 443520260
- Off-chain at
- 2026-08-26T11:10:10.888Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- Fje9BVMRV2i2HWws9NwPXZtm7FhKqCRiFjy8cNq8bQnA
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1026 chars)
{"actor":"reviewer","decided_at":"2026-08-26T11:10:10.780Z","decision":"review","investigation_id":"a11c7577-4338-477d-8f85-f61ec2de41f6","new_score":74,"page_slug":"hypurr-nfts","prev_score":74,"reason":"The page's core narrative — a legitimate Hyper Foundation NFT airdrop marred by a same-day $400K wallet-compromise theft flagged by ZachXBT, amid a cluster of Hyperliquid-ecosystem exploits — is well corroborated by multiple independent sources. However, four of eight timeline entries contain date or figure discrepancies: two ecosystem-context dates (Genesis Event, HyperEVM launch) use inaccurate day-level precision, the HyperVault date is off by two days from independent reporting, the 24-hour trading volume figure appears inflated relative to the majority-reported figure, and the floor-price-settlement entry directly contradicts the date stated in its own cited source.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}