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 · ORAMAMA X War-Panic Scam Network
- Sequence
- #4
- Score
- 2 → 2 (0)
- Cluster
- mainnet-beta
- Slot
- 457448122
- Off-chain at
- 2026-10-16T01:06:36.162Z
- Anchored at
- 2026-10-16T01:07:02.283Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- JBGZ1PtFYPgRetZRW9wzbfsyAapxDBQXdV4uz52qa9N
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2005 chars)
{"actor":"reviewer","artifact_identity":"2cfee67daa0fe21cc1528a01fe84d121","decided_at":"2026-10-16T01:06:35.957Z","decision":"review","disputed_pct":0.0952,"findings_hash":"Hs3AkYiXgan8Y7f3k15UAseJM7wvma2hhxYZPoqjXw17","investigation_id":"03c192ed-953c-4829-b6f7-e199e2fd5783","mode":"findings_only","new_score":2,"page_content_hash":"5aa75313b4e0b8f048771f5828376e95cc7775d32b75638e11045204096df985","page_slug":"oramama-x-war-panic-scam-network","prev_score":2,"reason":"The page's core narrative — a 10+ account X network buying aged accounts, fabricating AI personas (including the 'Wang Laurent'/Mario Nawfal persona), farming engagement with war-panic disinformation, and executing a coordinated $ORAMAMA pump-and-dump on February 22, 2026 before ZachXBT's March 23, 2026 disclosure — is well corroborated across eight to nine independent crypto-news outlets that all trace to the same underlying ZachXBT thread. Specific statistics (17 username changes, ~80,000 followers, 95-99% undersea-cable claim) check out against CoinPedia's reporting, though that outlet is not among the sources cited for the sections presenting those figures. Two defects recur: the page twice recasts what sourcing describes as aggregate multi-post engagement (26,000 retweets / 50,000 likes / 1.8 million views) as a single post, and it twice states as settled fact that X suspended all 16 flagged accounts, when the only source for this hedges with 'appears to have.' A further finding disputes the page's claim that X's product leadership referenced anti-bot/AI-labeling measures 'in response to coverage of the incident' — those measures were announced in February and early March 2026, before the network's March 23 disclosure. The cited on-chain pool address could not be independently verified because DexScreener, GeckoTerminal, and Solscan all blocked automated access.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}