Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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 · FixedFloat
View on Solana ↗
Sequence
#2
Score
10 → 10 (0)
Cluster
mainnet-beta
Slot
464261213
Off-chain at
2026-11-01T22:32:27.318Z
Anchored at
2026-11-01T22:32:32.000Z
Block time
2026-11-01T22:32:32.000Z

Independent verification

1. Database (off-chain)
4Zs38wzvEuL4JF9xgYKKJTiA347rHVdyeeLr25ayuS3t
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1525 chars)
{"actor":"reviewer","artifact_identity":"140bacab8ae98d98d5661e7321540c58","blocked_count":1,"decided_at":"2026-11-01T22:32:27.259Z","decision":"review","disputed_pct":0.4444,"findings_hash":"9AbZ9AhqQypnKoBVH7PsG35piKfU8DKD6t21AaV2uvzC","investigation_id":"6ac80542-8508-4b75-aa70-eaabfed272e6","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":10,"page_content_hash":"88efcd331ea4a2d1738c5dac22e172649f54a4181c83959ec00b2463f7f0071c","page_slug":"fixedfloat","prev_score":10,"reason":"Core facts hold: the February and April 2024 breaches, their amounts, eXch routing, and the Time4VPS account from FixedFloat's own post. The eXch takedown is dated 2024 on the page, but it happened on 30 April 2025, and that error appears in both the section and the timeline. The page also attributes the FixedFloat laundering link to the German authorities when it comes from analysts. It cites a 'privately to journalists' statement that is not in the source, and it places the two-month suspension after the February breach when it followed the April one. Checking was limited by blocked sources and partly relied on search summaries. Current status could not be determined.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":9,"sequence_num":2,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}