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 · LND
- Sequence
- #2
- Score
- 12 → 12 (0)
- Cluster
- mainnet-beta
- Slot
- 465082472
- Off-chain at
- 2026-11-03T23:24:36.525Z
- Anchored at
- 2026-11-03T23:24:52.000Z
- Block time
- 2026-11-03T23:24:52.000Z
Independent verification
- 1. Database (off-chain)
- 9wnkLpYa6NeLFhDrQCuB1iEZ23PG3tivarNfA1bDBXPZ
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1398 chars)
{"actor":"reviewer","artifact_identity":"abb4048e0d77ab77c7d2126ed1a8bd4e","decided_at":"2026-11-03T23:24:36.485Z","decision":"review","disputed_pct":0.6,"findings_hash":"8BJgXKx9XLBKi1XMr8G1zud2teQ1kbT6nmG6carAM2wX","investigation_id":"2f7c30c1-4224-4431-b322-5be4c94348e6","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":12,"omissions":{"material":0,"total":1},"page_content_hash":"b48858d508c12d3709edc26bf8d56a8abe5b1d20f1d1c16c9e20c8068de71292","page_slug":"lnd","prev_score":12,"reason":"The core incident (May 9, 2025 exploit via a modified onlyPool modifier, Pool Admin timeline, fund flows to TradeOrge and MEXC) matches the DeFiHackLabs and HackMD analyses. Two errors affect source attribution. The HackMD page is labeled the team's official postmortem and quoted for a DPRK statement, but it is an independent analysis with no DPRK mention. The $1.42M loss figure is credited to DeFiHackLabs, which says $1.27M. Several secondary claims (ZachXBT flag, Nameshift listing, Halborn recommendations, Drift attribution detail) were not verified.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":2,"subject_status":"shut_down","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}