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_approve · Compound V2
View on Solana ↗
Sequence
#3
Score
28 → 28 (0)
Cluster
mainnet-beta
Slot
426272424
Off-chain at
2026-06-13T20:35:02.712Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
3FFZ4aKCBcPBJv6Gxxgweu2sKFoipB3Wsk4SqbxQjAJZ
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1475 chars)
{"actor":"judge","decided_at":"2026-06-13T20:35:02.544Z","decision":"review_approve","investigation_id":"e3219d4b-6244-46ee-8372-f93fec77fb12","new_score":28,"page_slug":"compound-v2","prev_score":28,"reason":"The reviewer examined 22 claims and found zero disputed. All major incidents — the November 2020 oracle liquidation cascade ($89M), the September 2021 COMP distribution bug (~$80M at risk), the July 2024 governance attack (Proposal 289), the July 2024 website hijack, and the December 2025 V2 deprecation — are confirmed by Tier 1 sources. Six claims are partially supported, all involving minor date inaccuracies (claim_findings[18] places the X account hack in January 2023 rather than December 29, 2023; claim_findings[20] places Proposal 247's failure in July 2024 rather than May 2024; claim_findings[24] is off by one day on the Sonne Finance exploit) and one unverified attribution (claim_findings[22] names Consensys as a governance-attack critic where sources name OpenZeppelin's Michael Lewellen instead). None of these errors affect the factual integrity of the core allegations. Two high-priority coverage gaps (empty section content fields, absent TVL data) flag the page as structurally thin but do not undermine factual accuracy and are appropriate targets for future revision rather than grounds for denial.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}