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
- 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. - 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.
- 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 · LAB Token (LabsAI)
- Sequence
- #8
- Score
- 26 → 26 (0)
- Cluster
- mainnet-beta
- Slot
- 457496473
- Off-chain at
- 2026-10-16T04:01:21.792Z
- Anchored at
- 2026-10-16T04:01:38.737Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- Gc15tJk64j5wEJkuADN2PdrEHTfDCn9PEAgEme5orjae
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2081 chars)
{"actor":"reviewer","artifact_identity":"6f57aa770cf875bd69bbf317c390f3f1","decided_at":"2026-10-16T04:01:21.574Z","decision":"review","disputed_pct":0.08,"findings_hash":"Bazzfk6FHcTqAc8DTUXj9CDbbNb8EeW2skLvXT65ku6a","investigation_id":"4ae6cbec-29f1-4ae3-b338-d9feaa9ee725","mode":"findings_only","new_score":26,"page_content_hash":"aca89401e1db8bf829e4b6cf149653305614c37cd0da824b596bc1dedec0a423","page_slug":"lab-token-labsai","prev_score":26,"reason":"The large majority of this page's claims are well-supported: the TGE date and mechanics, the identities and follower counts of Sadkov and Mark X, the BVI shell company's registration details, the loan terms, the vesting manipulation details, the OTC discount mechanics, the Cookie DAO dispute, the Bitget/Shawn Liu/Gracy Chen allegations and exact quotes, the withdrawal and price-surge figures, and the Eesee background all check out against the cited sources and independent corroboration. Three issues stood out: (1) the claim that the project 'raised $1.5 million from institutional backers' appears to swap a retail/community-round figure for the actual $2.3 million institutional seed round led by Lemniscap; (2) the specific five-token list (RIVER, RAVE, SIREN, MYX, SKYAI) attributed to 'the same alleged market maker' conflates at least two distinct ZachXBT threads and omits tokens (COAI, M, PIPPIN) that were part of the actual list in one of them; (3) the May 3 mobile-app-launch date, while independently plausible, is not actually supported by its cited source, which was still describing the launch as 'imminent.' The 19,004-holder/0.35%-liquidity figures could not be independently verified. Most significantly, the page appears to stop tracking the story in mid-May 2026 even though it is now October 2026 and substantial further price collapse and apparent team changes occurred in the interim — this is the most important gap for a reader assessing current risk.","score_delta":0,"sequence_num":8,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}