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 · PRXVT
- Sequence
- #3
- Score
- 51 → 51 (0)
- Cluster
- mainnet-beta
- Slot
- 461974198
- Off-chain at
- 2026-10-27T06:46:44.544Z
- Anchored at
- 2026-10-27T06:46:59.000Z
- Block time
- 2026-10-27T06:46:59.000Z
Independent verification
- 1. Database (off-chain)
- BnhohHQ7SDPf3UucEewcs7Umb9sY53mCx17mmLewa6u1
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1470 chars)
{"actor":"reviewer","artifact_identity":"e89450fe461d0219717503da3fbf3326","blocked_count":2,"decided_at":"2026-10-27T06:46:44.357Z","decision":"review","disputed_pct":0.6364,"findings_hash":"BZUC9WXhgoHJxsv1XTEtYQmNPpA1JX4Heu1MDmFWVudu","investigation_id":"422ed46b-ac77-43f7-a2f6-63c1fb503dcc","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":51,"omissions":{"material":0,"total":1},"page_content_hash":"d53b113c99133abd8ad9130b56eeab33e5a84e424987851f51d242e06627af73","page_slug":"prxvt","prev_score":51,"reason":"The exploit mechanics and 32.8 ETH loss match the DeFiHackLabs PoC. Several claims fail: the ChainCatcher/Arkham VIRTUAL-to-Bybit item is from 2025-01-01, never mentions PRXVT, and is presented as incident-linked on the page. The BlockThreat entry date is wrong (published 2026-01-10) and the exploit date of 2026-01-05 conflicts with BlockThreat's 2026-01-01. The ATH figure is lower than CoinGecko's, and the market snapshot is stale. LP-removal, compensation and ZachXBT claims rest on unreadable X posts or are admitted as unverified. The subject-status search found nothing conclusive.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":11,"sequence_num":3,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}