Skip to main content
Sign in
← avoid.net

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

  1. 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.
  2. 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.
  3. 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 · 1inch
View on Solana ↗
Sequence
#2
Score
38 → 38 (0)
Cluster
mainnet-beta
Slot
426514404
Off-chain at
2026-06-14T23:15:54.919Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
9ghn8LCPfX4ShNEwyrku7d2dSq4MaP3UEPsocSmiucdk
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1980 chars)
{"actor":"reviewer","decided_at":"2026-06-14T23:15:54.866Z","decision":"review","investigation_id":"a4cc3a16-a934-40c9-8117-a05d45a1f6fd","new_score":38,"page_slug":"1inch","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. 1inch is a well-established, legitimate DeFi DEX aggregator launched in 2019, with 60%+ EVM DEX aggregator market share, 15+ security audits from top-tier firms (OpenZeppelin, ConsenSys, ABDK), and no evidence of fraud or self-dealing. The four incidents the page cites as driving the WARNING score are all either suffered by the entity or attributable to third-party failures: (1) the October 2024 Lottie Player frontend attack was a supply-chain compromise of a third-party npm library affecting the UI only; (2) the December 2024 private key incident affected a 1inch Labs resolver key but not user funds; (3) the March 2025 Fusion v1 exploit targeted a contract deprecated since 2023 being run by a third-party resolver, with ~90% of $5M recovered; (4) the TrustedVolumes incident — misdated by the page as 'May 2025' when it actually occurred May 7, 2026 — was explicitly disavowed by 1inch as a third-party resolver breach with zero impact on 1inch systems or user funds. The FSS Academy claim about co-founder Anton Bukov is an educational credential from 2011, not actionable evidence of misconduct. Under the AVOID.NET band semantics, a legitimate operator with material but largely third-party-caused caveats (deprecated-contract ecosystem risk, supply-chain frontend exposure) and an active security program belongs in CAUTIONARY (50-69), not WARNING. A score of 62 reflects these material but non-fraudulent caveats while correctly distinguishing a victim/bystander from a perpetrator.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}