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 · Tinyman
- Sequence
- #2
- Score
- 52 → 52 (0)
- Cluster
- mainnet-beta
- Slot
- 425436497
- Off-chain at
- 2026-06-10T00:27:48.393Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 6FPfQHPZ1WSKWQNwVACSsWHmbj6dqrnPU6dzHfej1adi
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (821 chars)
{"actor":"reviewer","decided_at":"2026-06-10T00:27:48.265Z","decision":"review","investigation_id":"0f8ef13b-c75f-411c-a011-e1e6771bb825","new_score":52,"page_slug":"tinyman","prev_score":52,"reason":"The Tinyman investigation page is broadly accurate and well-sourced. The most significant factual issue is a minor discrepancy in the primary attacker's transaction count (page says 16, TRM Labs reports 17). The $3M total loss figure is correct but the attribution of all losses to wrapped BTC/ETH overstates slightly since ALGO and arbitrage losses are included. One cited source (coin.fyi) now redirects to a 403-gated host, creating link rot for the v1.1 relaunch date claim.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}