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 · Genopets
- Sequence
- #3
- Score
- 42 → 37 (-5)
- Cluster
- mainnet-beta
- Slot
- 423648352
- Off-chain at
- 2026-06-01T18:41:19.027Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- EfqSSuGfAs74jNohiWS5rv93pFpU8ppphcVdMCncGNfy
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1240 chars)
{"actor":"judge","decided_at":"2026-06-01T18:41:18.913Z","decision":"review_revise","investigation_id":"9e8b0b91-f697-4da3-bb5d-d9b4366e3fd7","new_score":37,"page_slug":"genopets","prev_score":42,"reason":"The page is substantially accurate on its core claims — funding amounts, token price data, team backgrounds, and project milestones are all confirmed. One clear factual error was identified: claim_findings[18] states a '5 million GENE Lockdrop' but the official cited source explicitly specifies 10 million GENE. Additionally, claim_findings[15] overstates the STEPN MAU low figure (~30,000 vs. the confirmed ~43,000), and claim_findings[8] conflates two distinct token allocation buckets into a single 'Community Treasury 41%' figure. Two high-priority coverage gaps (ELITE token post-TGE status and on-chain token analysis) and the omission of a third co-founder (Jay Chang, coverage_gaps[0]) warrant revision before the page is considered complete. No link rot, no stale critical citations, and reviewer confidence is 0.82, supporting a minor-penalty revise rather than a stronger action.","score_delta":-5,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}