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 · LayerZero
- Sequence
- #2
- Score
- 38 → 38 (0)
- Cluster
- mainnet-beta
- Slot
- 426514787
- Off-chain at
- 2026-06-14T23:16:14.160Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 7b6NxRe8H5Nib2Q9vVMKkfafVMcmW8yBRY3vsSJ492wc
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1985 chars)
{"actor":"reviewer","decided_at":"2026-06-14T23:16:14.093Z","decision":"review","investigation_id":"ac519952-403c-434a-97fb-c421abbef480","new_score":38,"page_slug":"layerzero","prev_score":38,"reason":"Blue-chip calibration review (Prompt A). Verdict: over-penalized. Page content is treated as accurate; the trust_score band is miscalibrated. LayerZero is a legitimate, well-capitalized cross-chain messaging infrastructure company (Series A $135M, Series B $120M at $3B valuation) with no evidence of fraud, Ponzi mechanics, exit scam, or criminal convictions. The primary score driver is the April 2026 $292M KelpDAO exploit, which was executed by North Korea's Lazarus Group via social engineering of a LayerZero developer — a sophisticated state-sponsored attack suffered by the entity's ecosystem, not fraud perpetrated by LayerZero. LayerZero does bear partial negligence responsibility for approving risky 1-of-1 DVN configurations over 2.5 years and for initial blame-shifting before retracting on May 9, 2026. These are material security governance failures warranting a CAUTIONARY band, but they do not constitute fraud. The current WARNING band (20-49) conflates negligence-enabled hack victim with fraudulent actor. Under the post-policy band semantics, CAUTIONARY (50-69) is the correct placement: a legitimate operator with material, unresolved security concerns and a documented pattern of governance lapses. A score of 52 reflects the severity of the exploit and ongoing trust erosion from client departures while correctly distinguishing negligence from fraud. An outside skeptic can verify: (1) the Lazarus Group attribution via Chainalysis blog; (2) LayerZero's public apology quote via CoinDesk May 9, 2026; (3) ongoing institutional partnerships via BusinessWire February 2026; (4) no SEC/CFTC enforcement actions found.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}