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.

Sequence
#6
Score
52 → 52 (0)
Cluster
mainnet-beta
Slot
448957932
Off-chain at
2026-09-21T05:15:33.121Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
3RKL9VzZqNBZTU3KwQ36U3RTQUjKM7iR2RE9Nehpe2hS
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1978 chars)
{"actor":"reviewer","artifact_identity":"5493f6fff831c16615185e46900e60ff","decided_at":"2026-09-21T05:15:32.869Z","decision":"review","disputed_pct":0.2,"findings_hash":"67WHnNZFgu3B7CJaxNKi8Qq1DWxw9EtYoNiQFGaSoxhd","investigation_id":"7464bbaa-7441-4e83-b3cc-f24c6ed145fe","mode":"findings_only","new_score":52,"page_content_hash":"c6f9c5b1eeb5f98847a40fd5f21ec131ca68803a866da543cd87427f53715a44","page_slug":"internet-computer","prev_score":52,"reason":"The page is generally well-sourced and its central narrative — the 2021 launch, ~95% crash, Arkham's insider-wallet findings (with Arkham's own hedging faithfully preserved), the subsequent litigation and its procedural (not merits-based) dismissals in early-to-mid 2025, and the 2026 Mission 70 tokenomics reform — holds up well against independent verification, including a direct fetch of the primary Arkham report and multiple corroborating legal and news sources. Two clear factual errors were found: the CanisterWorm malware incident is dated 'In 2025' on the page when independent security research (JFrog, Security Boulevard, Aikido detection timeline) places it in March 2026, and the claimed 'total disclosed funding' of $164 million contradicts the page's own cited TechCrunch source, which explicitly states DFINITY had raised 'just over $195 million to date' at that point (Forbes independently reported a similar ~$190M figure the same week). The May 2026 price/market-cap snapshot could not be conclusively verified against a specific same-day historical data point, though secondary reporting suggests the true figures may have been somewhat lower than stated; this is flagged as unverifiable rather than disputed. Coverage gaps exist around formal regulatory history, independent replication of on-chain forensics, and quantified NNS voting-power concentration.","score_delta":0,"sequence_num":6,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}