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 · zkLend
- Sequence
- #3
- Score
- 50 → 50 (0)
- Cluster
- mainnet-beta
- Slot
- 464257223
- Off-chain at
- 2026-11-01T22:17:51.571Z
- Anchored at
- 2026-11-01T22:18:18.000Z
- Block time
- 2026-11-01T22:18:18.000Z
Independent verification
- 1. Database (off-chain)
- 9WKaES4PNPvEsZAeqb3mKGhecyLTH9VYaTJVLWyKeBSf
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1446 chars)
{"actor":"reviewer","artifact_identity":"d6521eb50f4ae788839179689754f23e","decided_at":"2026-11-01T22:17:51.507Z","decision":"review","disputed_pct":0.1111,"findings_hash":"3chJixkwBJF9cCNpLABCi6xw985MjDRPsca9vPKdFHeQ","investigation_id":"125788f2-a280-4a2b-b290-72b445456c7a","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":50,"omissions":{"material":0,"total":1},"page_content_hash":"08cfc8fdbb6af0d564651626664dd7af536568ee2c8ba3899a40a867e0f436d5","page_slug":"zklend","prev_score":50,"reason":"The core narrative (February 2025 roughly $9.5-9.57M exploit, failed Railgun and Tornado phishing laundering, June 25, 2025 shutdown with about $200K to users) is supported by reachable sources. Weaknesses: the exploit section contains cross-page editorial text ('the zklend page' / 'the zklend-starknet page') rather than direct statements, one archive URL points to an unrelated article, the $500,000 bounty and founder biographies were not confirmed by fetched sources, and the law-enforcement cooperation statement is missing. Only a sample of claims was checked in depth; no hard disputes found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"shut_down","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}