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_approve · Algorand
- Sequence
- #3
- Score
- 52 → 52 (0)
- Cluster
- mainnet-beta
- Slot
- 425423268
- Off-chain at
- 2026-06-09T23:00:32.476Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- B3kTSxx78Yg9Z9aKZaT97B7Wvk1bMr7YDiZ9jjBpeyaB
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1494 chars)
{"actor":"judge","decided_at":"2026-06-09T23:00:32.241Z","decision":"review_approve","investigation_id":"d8539e1f-0a5d-4cc9-b53a-813e6637aec7","new_score":52,"page_slug":"algorand","prev_score":52,"reason":"The review examined 37 claims and found 26 confirmed, 5 partially supported, 2 unverifiable, and 1 stale — zero outright disputed. The computed disputed_pct of 8% falls within the 0–10% approval band. The partially-supported findings (claim_findings[2], [13], [30], [36], [38]) are minor: a conflated Turing Award citation, unverified auction start price, overstated validator growth, imprecise headcount estimate, and a timeline that merges two separate corporate announcements by two months. The one stale finding (claim_findings[12]) is notable — the page's SEC regulatory section closes with a statement that no ruling has been confirmed, which the reviewer assessed as materially superseded by joint SEC-CFTC guidance in March 2026 classifying ALGO as a digital commodity. This stale claim sits in a high-severity section and is flagged as a high-priority coverage gap, but it reflects a significant post-investigation development rather than an error in the original investigation. No link rot was found. Reviewer confidence of 0.82 supports a firm approve. The page should be updated to reflect the March 2026 regulatory reclassification.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}