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 · NanoBit (Fake Crypto Platform — SEC Pig Butchering Judgment)
- Sequence
- #3
- Score
- 0 → 0 (-16)
- Cluster
- mainnet-beta
- Slot
- 465099917
- Off-chain at
- 2026-11-04T00:27:06.437Z
- Anchored at
- 2026-11-04T00:27:10.000Z
- Block time
- 2026-11-04T00:27:10.000Z
Independent verification
- 1. Database (off-chain)
- CJYvJQPBTdMLyMmAwBSxH5Jqagy1erD4gXJVkSWSNis
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1559 chars)
{"actor":"judge","artifact_identity":"96fcfcf613d59c2df9e20d9f95cda4c2","band_override":null,"decided_at":"2026-11-04T00:27:06.073Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.5833,"investigation_id":"a15fb769-6e8a-4ea7-b163-5c0555266b92","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":0,"page_slug":"nanobit-fake-crypto-platform-sec-pig-butchering-judgment","prev_score":0,"reason":"7 of 12 checked claims (58%) were disputed or could not be verified, which falls in the significant-issues band. The core of the page holds up: the June 16, 2026 default judgment, the $5,518,902 total and the per-defendant amounts match the SEC release (claim_findings[0]). The disputes are mostly date and citation errors, including the scheme start date (September 2023 on the page, October 2023 per the SEC) repeated in three places (claim_findings[3-5]), a wrong complaint date, and a mis-linked SEC release (claim_findings[1-2]). The Central District of California venue for Fei Liao's criminal case is not corroborated (claim_findings[6]), and the victim count and loss figure and the recovery commentary could not be verified (claim_findings[9-10]). Because the scheme-start error is one defect counted three times, the penalty sits at the lower end of the band.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":-16,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}