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_deny · PRXVT
- Sequence
- #4
- Score
- 51 → 51 (0)
- Cluster
- mainnet-beta
- Slot
- 461974203
- Off-chain at
- 2026-10-27T06:46:44.697Z
- Anchored at
- 2026-10-27T06:47:00.000Z
- Block time
- 2026-10-27T06:47:00.000Z
Independent verification
- 1. Database (off-chain)
- 7XTrWjqKPs2S7uoseE4CrDAhyADohJU6Zo9SWSJHcycY
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1595 chars)
{"actor":"judge","artifact_identity":"e89450fe461d0219717503da3fbf3326","band_override":null,"blocked_count":2,"decided_at":"2026-10-27T06:46:44.357Z","decision":"review_deny","delist_requested":true,"disputed_pct":0.6364,"investigation_id":"422ed46b-ac77-43f7-a2f6-63c1fb503dcc","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":51,"page_slug":"prxvt","prev_score":51,"reason":"Of 12 claims checked, 2 could not be read because the source blocked the reviewer and were left out of the count. Of the remaining 10, 5 were disputed and 2 could not be verified, giving 70% disputed or unverifiable. The disputed items include a ChainCatcher/Arkham VIRTUAL-to-Bybit transfer that dates from January 2025 and never mentions PRXVT (claim_findings[2] and [3]), an exploit date of 2026-01-05 that conflicts with BlockThreat's 2026-01-01 (claim_findings[5]), a wrong newsletter date (claim_findings[4]) and an understated all-time high (claim_findings[9]). The core exploit mechanics and the 32.8 ETH loss were confirmed (claim_findings[0]), so the penalty sits at the lower end of the band. The ZachXBT flag has no primary source (claim_findings[8]), and the LP-removal and compensation claims rest on X posts that could not be read. The omission and subject-status checks found nothing that changes the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":11,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}