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_revise · LAB / LABUSDT
- Sequence
- #3
- Score
- 8 → 0 (-14)
- Cluster
- mainnet-beta
- Slot
- 443512084
- Off-chain at
- 2026-08-25T07:12:40.604Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- DwQmGUkyGfDzq5XNHieX9FKh4yCtQMaBGLXAjdGcAeZT
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1823 chars)
{"actor":"judge","decided_at":"2026-08-25T07:12:40.214Z","decision":"review_revise","investigation_id":"61fd0b7f-7822-4972-a474-71aa01a222a1","new_score":0,"page_slug":"lab-labusdt","prev_score":8,"reason":"The review confirmed the large majority of the page's claims: 28 of 41 checked items were fully confirmed, including several direct quotes (loan interest terms, vesting-cliff changes, default clauses) that matched cited sources word for word. Disputed_pct is 14.6%, placing the page in the minor-issues band, but two of the three disputed findings are substantively serious rather than cosmetic. A claim that exchanges delisted LAB effective July 29, 2026 (claim_findings[31]) is unsupported by its own citation, uncorroborated anywhere else, and contradicted by live market data showing LAB still trading with volume in late August 2026 -- a false statement about an entity's current operational status that a reader could act on. Separately, the page states no public rebuttal from the LAB team was ever found (claim_findings[20]), yet one of the page's own cited sources quotes a team statement responding to the July crash -- an internal contradiction that unfairly omits the accused party's actual response. A third disputed item (claim_findings[28], a token-unlock timeline entry) cites an unrelated Bitget article, though the underlying unlock figure appears independently accurate. A dead citation (claim_findings[29], link_rot) and a high-priority coverage gap flagging the absence of independent on-chain verification for the page's core insider-supply allegations (coverage_gaps[0]) add further weight toward requiring revision before this page can stand as-is.","score_delta":-14,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}