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 · LAB Token (LabsAI)
View on Solana ↗
Sequence
#5
Score
40 (-7)
Cluster
mainnet-beta
Slot
423227483
Off-chain at
2026-05-30T20:18:25.846Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
H9Q1HDwKWLnNZCqCZGDk4LiHCZHRyjD54kbJzHan8bhp
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1340 chars)
{"actor":"judge","decided_at":"2026-05-30T20:18:25.679Z","decision":"review_revise","investigation_id":"4ae6cbec-29f1-4ae3-b338-d9feaa9ee725","new_score":0,"page_slug":"lab-token-labsai","prev_score":4,"reason":"The core allegations in this investigation — 95%+ insider supply control, $480 million withdrawal via 10 newly created wallets, a $6 billion FDV pump followed by a 65%+ crash, a BVI shell company, predatory 90% annualized loan terms, and unilateral vesting manipulation — are confirmed across multiple independent outlets. However, the reviewer identified two factual inaccuracies that require correction: claim_findings[3] and claim_findings[27] (timeline[2]) both incorrectly list OKX Wallet as a concurrent TGE listing venue when evidence consistently shows only six exchanges at launch and OKX Wallet entered as a product integration partner in November 2025; and claim_findings[7] understates total fundraising at $1.5 million when confirmed raises total approximately $4.65 million across three distinct rounds. These errors are peripheral to the investigation's central findings but affect the factual record and should be corrected before the page is considered fully accurate.","score_delta":-7,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}