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 · Griffain
- Sequence
- #3
- Score
- 47 → 37 (-10)
- Cluster
- mainnet-beta
- Slot
- 423639879
- Off-chain at
- 2026-06-01T17:45:19.551Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- AiLcS8dgQjgB2AxciqL5T9h7ECDR2TdVc8aWqh8vZiQR
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1658 chars)
{"actor":"judge","decided_at":"2026-06-01T17:45:19.293Z","decision":"review_revise","investigation_id":"498fedc8-482e-4ade-8b2c-fc92b781c433","new_score":37,"page_slug":"griffain","prev_score":47,"reason":"The review confirmed 18 of 28 claims and found broadly accurate core facts — platform launch dates, founder background, price history, and regulatory status all hold up. One claim is disputed (claim_findings[25]: the Bitget listing date recorded as December 11 is contradicted by Bitget's own records and a GlobeNewswire press release placing trading start on December 12, 2024), but this is a peripheral timeline date rather than a core allegation and carries low weight. The primary drivers for revision are three high-priority coverage gaps: the June 2025 acquisition of Privy by Stripe materially changes the third-party wallet-infrastructure dependency and is entirely absent from the page; the tokenomics distribution (40/30/20/10) is sourced entirely from project-provided claims with no independent on-chain verification; and no named auditor or public audit report has been identified for the smart contracts. Three additional claims are unverifiable (fair-launch mechanics, native staking APY, transaction count timing). A -10 score modifier reflects the combination of one disputed peripheral fact, three unverifiable claims, and material omissions at high priority — none of which individually justify denial, but collectively indicate the page needs targeted updates before it is fully reliable.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}