Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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
View on Solana ↗
Sequence
#5
Score
65 → 65 (0)
Cluster
mainnet-beta
Slot
457843383
Off-chain at
2026-10-17T00:50:34.403Z
Anchored at
2026-10-17T00:50:46.930Z
Block time
—

Independent verification

1. Database (off-chain)
HtyNjJ5iARCF2CCJzTAMyBqSo9GGkd1NLn3pFKpoQ1K8
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1818 chars)
{"actor":"reviewer","artifact_identity":"9514a85fdc27c40a43ad6d9ddfcee586","decided_at":"2026-10-17T00:50:34.232Z","decision":"review","disputed_pct":0.55,"findings_hash":"ASXwYPbZ2CvsXsUwqyXWfQg7AFAsAGUjitQWrCNK1qgf","investigation_id":"161be9c7-ee67-4ea2-9533-68617b497f21","mode":"findings_only","new_score":65,"page_content_hash":"fa43d5a99ef45592fe8e8010b297c0250d471922561f3ad9eceaa51ca0cacee5","page_slug":"subquery-network","prev_score":65,"reason":"The page's core narrative -- SubQuery's founding team, funding history, mainnet/token launch, and the April 2026 smart-contract exploit mechanics and compensation -- is substantially corroborated by the company's own disclosures and independent trackers. However, several specific figures do not hold up under check: the stated 2% SQT inflation rate contradicts SubQuery's own public sale terms (~1.3%), the company's headquarters is stated as New Zealand in two places when SubQuery's current documentation says Singapore, two of the five exploit transaction timestamps do not match the primary incident report's own timeline, and the ATH price/date pairing in the timeline conflates figures from two different trackers. The ZachXBT attribution appearing in both the summary and the exploit section could not be corroborated by any source, including the section's own cited sources, and should be treated as unverified pending a direct citation. The tokenomics percentage breakdown and a few timeline dates/prices (Series A exact date, Bybit launch price, year-end 2024 price) could not be independently confirmed. The Audit History section omits a relevant intervening 2024 audit mentioned in the primary disclosure.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}