Skip to main content
Sign in
← 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 · Compound V2
View on Solana ↗
Sequence
#2
Score
28 → 28 (0)
Cluster
mainnet-beta
Slot
426272422
Off-chain at
2026-06-13T20:35:02.630Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
9uzq8CdM3VEthaRYsayoDZhm9mHgiYYAj9KdoXJmBHTP
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1300 chars)
{"actor":"reviewer","decided_at":"2026-06-13T20:35:02.544Z","decision":"review","investigation_id":"e3219d4b-6244-46ee-8372-f93fec77fb12","new_score":28,"page_slug":"compound-v2","prev_score":28,"reason":"The Compound V2 investigation page is factually well-grounded overall, with all major incidents (oracle liquidation cascade, COMP distribution bug, governance attack, website hijack, X account hack, V2 deprecation) independently verified. The primary accuracy concerns are date errors in the timeline — the X account hack is dated January 2023 when it occurred December 29, 2023; Proposal 247 failure is dated July 2024 when it failed May 2024; and the Sonne Finance exploit is dated May 16 when the consensus date is May 15. One compound claim about COMP being returned (37,493 tokens by two users) may conflate a drain event with returns. Attribution of the governance attack characterization to 'Consensys' is unverified — named critics are OpenZeppelin's Lewellen, Wintermute, and Gauntlet. The most significant structural issue is that all section content fields are empty, leaving the page as a summary and timeline only with no explanatory prose.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}