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.

Decision
review_revise · RaveDAO
View on Solana ↗
Sequence
#9
Score
26 → 26 (0)
Cluster
mainnet-beta
Slot
464263755
Off-chain at
2026-11-01T22:41:28.638Z
Anchored at
2026-11-01T22:41:39.000Z
Block time
2026-11-01T22:41:39.000Z

Independent verification

1. Database (off-chain)
HE7X3mH6S8kFXc1EMA3EDxfUtv65BskiyVcEGVF3Nr3c
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1413 chars)
{"actor":"judge","artifact_identity":"0f61e47a283154f5588fc59834e68cda","band_override":null,"decided_at":"2026-11-01T22:41:28.292Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.25,"investigation_id":"4c048eca-2d76-4dc0-8d13-8b90862d3449","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"page_slug":"ravedao","prev_score":26,"reason":"The core account (April 2026 price spike and collapse, ZachXBT's allegations, the Binance and Bitget investigations, and the team's denial) was confirmed against CoinDesk and The Block (claim_findings[0], [7]), and the page presents it as allegation. Two of eight claims could not be verified (claim_findings[2], the CoinDesk attribution for the bounty, and claim_findings[5], the early-June price snapshot), which puts the disputed share at 25%. Separately, the CoinGecko all-time high and low figures are out of date (claim_findings[3], [4]) and the CoinJournal archive link points to an unrelated article (claim_findings[6]). These are peripheral to the main allegations, and the reviewer's confidence was low (0.5), so the penalty sits at the mild end of the minor band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":9,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}