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
- Sequence
- #3
- Score
- 2 → 2 (0)
- Cluster
- mainnet-beta
- Slot
- 426254870
- Off-chain at
- 2026-06-13T18:39:09.610Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- Ci1HodL2CNUakd8YA9uFM8y2umGFCGEBceeJsaH4Jd1i
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1273 chars)
{"actor":"judge","decided_at":"2026-06-13T18:39:09.363Z","decision":"review_approve","investigation_id":"c65a2c9b-9cdf-4c29-af19-336a0bd6cb06","new_score":2,"page_slug":"donald-basile-bitcoin-latinum-ltnm-monsoon-blockchain-corporation","prev_score":2,"reason":"The reviewer confirmed 21 of 24 claims outright and found zero disputed claims, giving a disputed_pct of 0%. The three partially-supported findings (claim_findings[18]: Fusion-io IPO role overstated; claim_findings[20]: Hellmuth bracelet count stale at 16 vs. 17; claim_findings[21]: 'GENESIS' event name unconfirmed in primary press releases) are minor biographical or peripheral details that do not affect any of the core fraud allegations, the SEC enforcement record, or the civil litigation history. No link rot, stale citations, or unverifiable claims were identified. Two high-priority coverage gaps exist — on-chain token analysis and status of the April 2026 SEC enforcement action — but gaps indicate opportunities for expansion rather than grounds for denial, particularly given the complaint is less than two months old. Reviewer confidence was high at 0.87.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}