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
60 → 60 (0)
Cluster
mainnet-beta
Slot
457849570
Off-chain at
2026-10-17T01:12:55.927Z
Anchored at
2026-10-17T01:13:08.794Z
Block time
—

Independent verification

1. Database (off-chain)
7Rq7prYzmxgGTd8eUgbfmL6N6JzpaHSvAQwKRcmxeYAc
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1967 chars)
{"actor":"reviewer","artifact_identity":"8ee248f97cba750b3bf7666b447cac74","decided_at":"2026-10-17T01:12:55.782Z","decision":"review","disputed_pct":0.2353,"findings_hash":"AWy9RTANH1rudmk7Khq7rALEjrP5rsiNPBG2qGkUm18Q","investigation_id":"3e4567af-0a09-4107-b598-0cddbf8e26fa","mode":"findings_only","new_score":60,"page_content_hash":"289c303766186276bcd9a979313f46a463049b1bba4c6a72a7980ee501ed25d3","page_slug":"curve-dex","prev_score":60,"reason":"The page's core narrative — the July 2023 Vyper reentrancy exploit, its recovery, the DAO compensation vote, and Michael Egorov's recurring CRV-collateralized liquidations — is well supported by its cited sources, and several figures were independently corroborated beyond the citations given (pool-by-pool losses, bounty amounts and dates, the 2020 CRV/DAO deployment story, the 2025 X/DNS incidents, and the 2025 CRV inflation cut). Two defects recur across multiple locations: a '53 investors' figure that belongs to a later, larger cumulative CRV sale is misattached to an earlier $42M tranche in both a section and the timeline, and the December 2024 liquidation is characterized as 'a repeat of the earlier episode' when it was in fact about 160 times smaller than the June 2024 event and CoinDesk did not use that framing. A specific '$11.5 million' Curve Lend bad-debt figure could not be traced to any source, cited or independent, and conflicts in granularity with the better-supported ~$10 million figure used elsewhere on the page. The '427.5 million CRV' pledged-collateral figure is only partially supported, since the page's own cited source gives a different token count for the same 47%-of-supply claim. None of these issues are fabrications; they read as compounding errors from synthesizing multiple overlapping news cycles about the same ongoing story.","score_delta":0,"sequence_num":6,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}