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 · SubQuery Network
- Sequence
- #3
- Score
- 50 → 38 (-12)
- Cluster
- mainnet-beta
- Slot
- 443525159
- Off-chain at
- 2026-08-27T10:25:12.922Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- BBguuM4irFPDXEAHcJfFEwRyXPkGXRqmTmoeLH5EJFEL
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1683 chars)
{"actor":"judge","decided_at":"2026-08-27T10:25:12.457Z","decision":"review_revise","investigation_id":"161be9c7-ee67-4ea2-9533-68617b497f21","new_score":38,"page_slug":"subquery-network","prev_score":50,"reason":"Recomputing from the claim_findings array (not the mismatched summary block) gives 4 confirmed, 2 partially_supported, 1 unverifiable, 0 disputed out of 7 claims, for a disputed_pct of (0+1)/7 = 14.3% — squarely in the 10-30% minor-issues band. The page's central material — SubQuery's founding, funding, its 2022 audit, and the April 2026 exploit mechanics and compensation — is confirmed against both the entity's own disclosure and independent analysis (claim_findings[0], [2], [4], [5]). Two claims carry dating and internal-arithmetic errors that were correctly kept out of the numerator as partially_supported rather than disputed (claim_findings[1]'s seed-round date, claim_findings[3]'s ATH date and its 76%-vs-65% decline inconsistency). The one claim driving the disputed_pct is claim_findings[5], an unverifiable attribution crediting ZachXBT with flagging this incident — the reviewer found no supporting source anywhere, including ZachXBT's own archive, and 'unverifiable' rather than 'disputed' is the correct call since absence of corroboration is not a contradicting source. That single claim names a real individual in an attribution nobody can substantiate, which is why the delta sits at the harsher end of the minor-issues band despite the low sample size and the reviewer's own reduced confidence (0.65).","score_delta":-12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}