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
#9
Score
63 → 63 (0)
Cluster
mainnet-beta
Slot
464292603
Off-chain at
2026-11-02T00:24:27.705Z
Anchored at
2026-11-02T00:24:34.000Z
Block time
2026-11-02T00:24:34.000Z

Independent verification

1. Database (off-chain)
2KrZQjWXQUA5CwjQynkdH5fVUX8rsy68WDSfTdMUVbkm
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1474 chars)
{"actor":"reviewer","artifact_identity":"de56e5832519b5e5a2cccf67cb3bc9a0","blocked_count":1,"decided_at":"2026-11-02T00:24:27.645Z","decision":"review","disputed_pct":0.3636,"findings_hash":"8MaxFQjiKZEX5MVgGZ6Xhx2zX5HM7LgTP8kKUVo8etJF","investigation_id":"3e4567af-0a09-4107-b598-0cddbf8e26fa","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":63,"omissions":{"material":1,"total":1},"page_content_hash":"289c303766186276bcd9a979313f46a463049b1bba4c6a72a7980ee501ed25d3","page_slug":"curve-dex","prev_score":63,"reason":"The core narrative holds: the Vyper reentrancy exploit, the roughly 73% recovery by Aug 7, the June 2024 roughly $140M founder liquidation and the May 2025 DNS hijack all match the sources I fetched. Errors found: the 10% bounty deadline is given as August 4 in three places but sources give 08:00 UTC August 6; a TechCrunch attribution is not what the article says; the December 2024 liquidation is under $1M but is framed as a repeat; and bad-debt figures vary across sources. The page omits the UwU Lend context for the June 2024 event. Only a sample of the page's claims was verified.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":11,"sequence_num":9,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}