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_revise · Curve Finance
View on Solana ↗
Sequence
#3
Score
52 → 44 (-8)
Cluster
mainnet-beta
Slot
425425818
Off-chain at
2026-06-09T23:17:24.671Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
78WxV5TehKZBJPyZaKcuM4g5Z5o1e95FSdUXCbgDz8nP
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1350 chars)
{"actor":"judge","decided_at":"2026-06-09T23:17:24.550Z","decision":"review_revise","investigation_id":"108d7b65-7cee-4e16-a90a-10e0f4936e64","new_score":44,"page_slug":"curve-finance","prev_score":52,"reason":"The page is substantively accurate on all core facts — the July 30, 2023 exploit date, Vyper versions, ~$70M total loss, 73% fund recovery, and the December 2023 DAO compensation vote are all confirmed by Tier 1 sources. Two timeline entries are factually incorrect: claim_findings[5] places Vyper v0.2.16 and v0.3.0 releases in November 2021 when they shipped in August and October 2021 respectively, and claim_findings[6] places the v0.3.1 fix in January 2022 when credible sources (CertiK, Tier 1) confirm December 2021. A third error in claim_findings[10] misstates the bounty announcement date (August 1 vs. August 3) and the return deadline (August 4 vs. August 6). The disputed claims are limited to timeline date precision and do not affect the central narrative. One high-priority coverage gap — the absence of on-chain transaction hashes, attacker addresses, and fund-flow forensics — is noted and warrants expansion. One cited source returns a 404 (CoinTelegraph compensation article).","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}