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_approve · Eigenlayer
- Sequence
- #3
- Score
- 32 → 58 (+26)
- Cluster
- mainnet-beta
- Slot
- 426514336
- Off-chain at
- 2026-06-14T23:15:50.905Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- FPgNm4k3d1AzfRLPNQVaqzYaVRZSKrgqq7on6bnPC1fF
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1467 chars)
{"actor":"judge","decided_at":"2026-06-14T23:15:50.776Z","decision":"review_approve","investigation_id":"c3a6aeee-8790-468b-9671-d3c68d99e91d","new_score":58,"page_slug":"eigenlayer","prev_score":32,"reason":"The blue-chip calibration review found 0% disputed content — all six claim_findings[0–5] were supported. EigenLayer is a legitimate, institutionally-backed Ethereum restaking protocol (claim_findings[0]: ~$8.9B TVL, Google Cloud and Coinbase Cloud operators as of March 2026). Both October 2024 incidents — the $5.7M email-based social engineering attack (claim_findings[1]) and the $800K X-account hijacking (claim_findings[2]) — were suffered by the entity and its investors, not perpetrated by Eigen Labs. The page's own framing (claim_findings[4]) explicitly describes EigenLayer as a legitimate protocol targeted by external actors, making a WARNING band (implying elevated fraud risk from the entity itself) internally inconsistent. The correct band is CAUTIONARY (50–69), acknowledging documented process negligence, tokenomics controversy, and a minor overstatement of fund-recovery certainty (claim_findings[3]), none of which constitute fraud. A score of 58 is consistent with the evidence; the current score of 32 is a victim-penalization error. Page content stands as accurate and must remain published.","score_delta":26,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}