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 · Granary Finance (GRAIN)
- Sequence
- #3
- Score
- 42 → 42 (0)
- Cluster
- mainnet-beta
- Slot
- 425423827
- Off-chain at
- 2026-06-09T23:04:14.885Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 4GDGpKr1Qi4nY94SJvXqcaDKUqsRSHcJoURutruuR2zA
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1273 chars)
{"actor":"judge","decided_at":"2026-06-09T23:04:14.644Z","decision":"review_approve","investigation_id":"b0060f35-3a80-4f11-a85e-257838325927","new_score":42,"page_slug":"granary-finance-grain","prev_score":42,"reason":"The reviewer examined 26 claims and found zero disputed. Twenty claims were fully confirmed by independent sources, four were partially supported with only minor precision issues (a ~$16K TVL figure discrepancy in claim_findings[12], the 'CEO' title for Justin Bebis in claim_findings[7], a one-month uncertainty on the Cod3x merger date in claim_findings[22], and the March 3 launch-asset specifics in claim_findings[6]), and two were unverifiable absence-of-evidence claims (no direct contract hack in claim_findings[15]; market cap ranking in claim_findings[21]). The single instance of link rot affects a secondary BSC News citation that is corroborated by a Tier 1 Blockworks source. All five coverage gaps carry medium or low priority and suggest expansion rather than correction. With a disputed_pct of 7.7% and reviewer confidence of 0.82, the page meets the threshold for approval without modification.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}