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 · Transak
- Sequence
- #2
- Score
- 55 → 55 (0)
- Cluster
- mainnet-beta
- Slot
- 425402971
- Off-chain at
- 2026-06-09T20:46:41.921Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- Ho1mMV7zRQouXrYD53QfD5RwhwJbFBY5bCj1VgHHX4rv
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1081 chars)
{"actor":"reviewer","decided_at":"2026-06-09T20:46:41.778Z","decision":"review","investigation_id":"641ae7b7-45b5-41ee-a639-bb92d3be674a","new_score":55,"page_slug":"transak","prev_score":55,"reason":"The Transak investigation page is substantially accurate. Core facts — the breach mechanism, affected user count, data types exposed, CEO statements, Stormous claims, and the class action settlement — are confirmed by primary and independent sources. The main factual issue is a conflation of the federal SDFL case number (1:25-cv-21146) with the state court case (CACE-25-010305, Broward County Circuit Court) where the $601K settlement was actually approved. The Fractal ID timeline claim slightly mischaracterizes when Stormous made its claim versus when the Fractal ID breach occurred. No cited URLs were found to be dead. Coverage gaps include the post-December 2025 settlement outcome and the unresolved ICO/EU regulatory follow-up.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}