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 · Level Finance
- Sequence
- #3
- Score
- 58 → 58 (0)
- Cluster
- mainnet-beta
- Slot
- 464345574
- Off-chain at
- 2026-11-02T03:33:22.517Z
- Anchored at
- 2026-11-02T03:33:47.000Z
- Block time
- 2026-11-02T03:33:47.000Z
Independent verification
- 1. Database (off-chain)
- 4q78LRVsCbuPELt2qENkLPyZ1ibg2KdcQJ93La2dcmBv
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1398 chars)
{"actor":"reviewer","artifact_identity":"e0918f2dbfef6868afed7844ff5847ae","blocked_count":1,"decided_at":"2026-11-02T03:33:22.471Z","decision":"review","disputed_pct":0.25,"findings_hash":"3ycERj2iPDSDtBBNZZ1yHhZTCMoKJD3E6R5pzPrZRYJE","investigation_id":"53923a2d-772b-4381-9593-9fa355fc6d98","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":58,"omissions":{"material":0,"total":1},"page_content_hash":"7ae564dceaa0ec99e4c6e44e29a085c027e141cde0bcc2a5d2956fe8bee66553","page_slug":"level-perps","prev_score":58,"reason":"The core May 2023 exploit narrative (date, amounts, contract, function, team statements, DAO proposal) matches BleepingComputer and Cointelegraph. Errors: the 25% post-exploit price drop contradicts sources and the page's own timeline (~50%). Some attributions are loose (Halborn on audit-timing uncertainty, 'smaller' attempt), market figures are stale, the ZachXBT flag is unsupported, and dormancy metrics could not be checked because DefiLlama returned 403. No evidence of a shutdown or later exploit was found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":8,"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}