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 · Misam M. Abidi
- Sequence
- #3
- Score
- 2 → 0 (-12)
- Cluster
- mainnet-beta
- Slot
- 443513800
- Off-chain at
- 2026-08-25T12:04:51.682Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- BVazdMKevAPg8qsGgeNhHqqZRcyeKJgFRZWn5Yui39pm
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2339 chars)
{"actor":"judge","decided_at":"2026-08-25T12:04:51.466Z","decision":"review_revise","investigation_id":"5f4587a9-ca84-4206-9973-5380ae7d6285","new_score":0,"page_slug":"misam-m-abidi","prev_score":2,"reason":"The page's central factual backbone -- the federal indictment's charges, penalties, prosecuting agencies, alleged scheme mechanics, and the state action's dollar figures -- is solidly confirmed against primary DOJ, IRS, and TDCI sources (claim_findings[0], [1], [2], [4], [7], [8], [9], [12], [14]). However, the reviewer read the actual Tennessee Chancery Court injunction the page itself cites and found two checkable errors: the page says the asset-freeze injunction was 'obtained' in May 2024 when the court order shows it was issued March 22, 2024 following a December 2023 TRO -- the page conflated a court date with a press-release date (claim_findings[5]). More significantly, the page states the NUME token was 'fully owned and controlled' by Galani and both Abidis, but the same court's sworn stipulated facts say NumisMe (NUME's issuer) was wholly owned by Misam Abidi alone, with Galani only a bank signatory and Anisha Abidi not implicated in that entity at all (claim_findings[6], echoed in [13]). That over-attributes conduct to two other named people. This error traces to language in TDCI's own press release, which the page also cites, so the page repeated an official source's imprecision rather than inventing it -- a mitigating factor, but not a full excuse given the more specific primary document was available and used elsewhere on the page. A third disputed item, an incorrect implication that Abidi appears on the August 2026 primary ballot, is a lower-stakes procedural error unrelated to anyone's conduct (claim_findings[11]). With 15 total claims, this basket of errors computes to a 26.7% disputed/unverifiable rate, near the top of the minor-issues band; the small claim count means each error carries outsized arithmetic weight, but the substance -- one date error, one attribution error mitigated by its official-source origin, one ballot-procedure error -- warrants correction rather than escalation to a significant-issues or failed-factcheck outcome.","score_delta":-12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}