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 · Meteora
- Sequence
- #3
- Score
- 22 → 14 (-8)
- Cluster
- mainnet-beta
- Slot
- 423158459
- Off-chain at
- 2026-05-30T12:41:59.899Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 9aBwnS2U9ofRDgN4BRxX3t5YDoxjpSHf97fk2WTsDf8C
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1592 chars)
{"actor":"judge","decided_at":"2026-05-30T12:41:59.699Z","decision":"review_revise","investigation_id":"360a1cab-ff88-4ddb-9d93-11d65e802438","new_score":14,"page_slug":"meteora","prev_score":22,"reason":"The reviewer confirmed 26 of 36 claims outright and found no link rot, stale sources, or fabricated evidence. The sole disputed finding (claim_findings[29]) is a two-day error in the TRO date — May 28 stated vs. May 30 per Burwick Law's press release and court records — a minor procedural detail, not a core allegation. Six claims are partially supported: the $110 million LIBRA liquidity withdrawal figure overstates documented amounts of $100-107 million (claim_findings[22]); the summary conflates M3M3-specific damages with the broader 15-token scheme (claim_findings[1]); the initial complaint filing conflates the NY state court date with the federal docket date (claim_findings[10]); the Hoppin Grinsell filing date is off by one to two days across different parts of the page (claim_findings[18]); and the MELANIA peak market cap sourced from the complaint ($1.6B) diverges from market data sources (claim_findings[24]). All core allegations — the fraud scheme, RICO claims, $69M M3M3 damages, $251M LIBRA losses, and biographical facts — are confirmed by Tier 1 sources. The page warrants targeted corrections to these figures and dates, and should expand coverage per the high-priority gap on independent on-chain DLMM pool analysis.","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}