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 · WEMIX / WEMIX$ Stablecoin
- Sequence
- #5
- Score
- 26 → 26 (0)
- Cluster
- mainnet-beta
- Slot
- 457962697
- Off-chain at
- 2026-10-17T08:00:29.922Z
- Anchored at
- 2026-10-17T08:01:00.716Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 7etFj8upWEhmMdbxcTwdzmuUWiZsuRh5eufiLrHUtCZ3
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2329 chars)
{"actor":"reviewer","artifact_identity":"750bb98374d7752a9ba82eeeb719c82a","decided_at":"2026-10-17T08:00:29.743Z","decision":"review","disputed_pct":0.25,"findings_hash":"BysQxGPLbugTveoZM2r9iX5vRFb1ZAg3n2g7Ukn1RVZB","investigation_id":"6a784339-9712-41d2-8a47-0a6059ddf02f","mode":"findings_only","new_score":26,"page_content_hash":"6df2c5a4eda796f0c9399322749a06d3e38e317deb5d9634eb8619d75e015f68","page_slug":"wemix-wemix-stablecoin","prev_score":26,"reason":"The page's core narrative — three governance/security failures since 2022, two hacks, two DAXA delistings upheld through two rounds of litigation — is well supported by the cited reporting and independently verifiable court records; dates, court divisions, price-crash magnitudes, and quoted CEO rationale all check out closely against primary and tier-1 sources. Several issues were found: (1) a specific, quotable user-growth statistic (417K to 5.42M, +1,200% YoY) appears in both the summary and Platform Overview but is absent from its own cited sources and uncorroborated elsewhere — likely unsupported; (2) the '$6.25 million total estimated loss' for the July 2026 exploit conflates the face value of unauthorized minting with the much smaller (~$724K) amount actually bridged off-chain, a distinction several of the page's own cited outlets draw explicitly; (3) the February 2025 hack narrative asserts the leaked keys were uploaded to a shared repository 'as early as mid-2023,' which is both internally inconsistent with the same sentence's 'two months to plan' and contradicted by the cited Halborn report, which places the key theft about two months before the hack; (4) a timeline entry misattributes a Nov. 24, 2022 price crash ($1.55→$0.46) to the Dec. 8, 2022 court-ruling date, a date and causal attribution directly contradicted by the page's own cited CoinDesk article; (5) a cited source (bitcoinworld.co.in) used for two sections now returns HTTP 410 Gone, though a working Wayback snapshot is already recorded in sources_used and could directly replace it; (6) WEMIX.Fi TVL-drop (66%) and WEMIX$ one-week devaluation (98.9%) figures could not be verified against any source actually cited by the page.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}