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 · DAO Maker Vesting
View on Solana ↗
Sequence
#3
Score
2222 (0)
Cluster
mainnet-beta
Slot
426265558
Off-chain at
2026-06-13T19:49:46.365Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
wSyZbBeF3FbS9299q69yfdtJA5Rikv3feZkoRkMpSCW
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1204 chars)
{"actor":"judge","decided_at":"2026-06-13T19:49:46.062Z","decision":"review_approve","investigation_id":"d8c26836-fed6-47ab-a999-8ba0da02fedf","new_score":22,"page_slug":"dao-maker-vesting","prev_score":22,"reason":"The reviewer found zero disputed claims across 14 checked items. All core allegations — the August and September 2021 hack amounts, victim counts, technical exploit vectors, Tornado Cash laundering, and unmet compensation commitments — are confirmed by Tier 1 and Tier 2 sources including CoinDesk, Decrypt, Newsweek, and SlowMist. Three claims are partially supported due to minor date inaccuracies: the CoinTelegraph article date (April 23 vs. April 1 in claim_findings[11]) and the OKX delisting dates (January 27-30 vs. January 1 in claim_findings[12]). Neither inaccuracy affects the substance of the underlying events. Two high-priority coverage gaps exist — missing on-chain transaction references and empty page sections — but these represent expansion opportunities rather than factual failures, and do not meet the threshold for revise.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}