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 · Linea
- Sequence
- #5
- Score
- 44 → 58 (+14)
- Cluster
- mainnet-beta
- Slot
- 426514828
- Off-chain at
- 2026-06-14T23:16:15.730Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- A6oxz2ZdfDZyorGo3detzGJd5kRVjGqsfVGPKkY3JcRQ
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1571 chars)
{"actor":"judge","decided_at":"2026-06-14T23:16:15.604Z","decision":"review_approve","investigation_id":"99e611fa-735f-4e43-898e-c8918917dc99","new_score":58,"page_slug":"linea","prev_score":44,"reason":"This is a severity-calibration adjudication. The reviewer found 0% disputed claims — all six claim_findings are supported — and concluded the current score of 44 (WARNING) is too harsh for a legitimate, actively-used Layer 2 platform. Three specific miscalibration factors justify the positive delta: (1) claim_findings[0] confirms the Velocore hack loss is attributable to a third-party smart contract bug, not Linea code, making the sequencer halt a protective intervention rather than a failure; (2) claim_findings[1] confirms the Consensys/SEC action was fully dismissed in February 2025 with no fines, making it a stale risk factor still weighing on the score; and (3) claim_findings[3] and [5] document substantial enterprise legitimacy signals — SWIFT's 30+ bank prototype, $1B+ TVL at peak, and major DeFi protocol deployments — absent from the current risk weighting. The remaining real risk is the confirmed Stage 0 centralization classification (claim_findings[2]), which correctly prevents a higher band but does not warrant WARNING. A score of 58 (CAUTIONARY) accurately reflects a legitimate platform with disclosed, structural centralization risk and one operationally chaotic but non-fraudulent token launch.","score_delta":14,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}