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 · SubQuery Network
- Sequence
- #2
- Score
- 50 → 50 (0)
- Cluster
- mainnet-beta
- Slot
- 443525155
- Off-chain at
- 2026-08-27T10:25:12.804Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- CvajtjbLd7d1VnMLLsxiNwhNkAgRZW3iijAbxqgjHQG7
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1034 chars)
{"actor":"reviewer","decided_at":"2026-08-27T10:25:12.457Z","decision":"review","investigation_id":"161be9c7-ee67-4ea2-9533-68617b497f21","new_score":50,"page_slug":"subquery-network","prev_score":50,"reason":"This is a thin page (no section body text, only source lists, and an empty top-level sources_used array), so only 7 checkable atomic claims could be extracted, drawn almost entirely from the summary and timeline. The core narrative — founding, funding rounds, 2022 audit, and the April 2026 exploit mechanics and remediation — is well corroborated by SubQuery's own disclosures and independent sources. Two claims show internal or dating inconsistencies (a placeholder seed-round date and an ATH price that is correct in value but wrong in date, plus an internally inconsistent decline percentage), and the claim that ZachXBT flagged the incident could not be corroborated anywhere.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}