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 · Mantle
View on Solana ↗
Sequence
#4
Score
48 → 48 (0)
Cluster
mainnet-beta
Slot
426514901
Off-chain at
2026-06-14T23:16:20.375Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
BoKx8TyYAZKU63e9zwspRPfdFAUiVbG8eo46Md8PipHZ
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1884 chars)
{"actor":"reviewer","decided_at":"2026-06-14T23:16:20.308Z","decision":"review","investigation_id":"54f4170c-3817-4555-85dc-b8678b640860","new_score":48,"page_slug":"mantle","prev_score":48,"reason":"Blue-chip calibration review (Prompt A). Verdict: over-penalized. Page content is treated as accurate; the trust_score band is miscalibrated. Mantle is a legitimate Ethereum Layer 2 operator (EVM-compatible, OP Stack, ZK validity proofs via OP-Succinct as of September 2025) with $1.32B TVL per L2Beat, $6B+ treasury inherited from BitDAO, multiple professional security audits (OpenZeppelin, Secure3, Sigma Prime, Mixbytes), and zero regulatory actions from SEC, CFTC, or DOJ. The two incidents driving the current WARNING score — the $24M mETH loss in the February 2025 Bybit hack and the April 2026 KelpDAO rsETH $292M exploit — were both caused by third parties (North Korean hackers against Bybit; LayerZero DVN infrastructure compromise against KelpDAO) rather than by Mantle's own fraud or negligence. Mantle in fact responded constructively to the KelpDAO crisis by proposing a 30,000 ETH credit line to Aave DAO, which passed governance. Real and material risks do exist: L2Beat confirms zero-delay contract upgrades (CRITICAL flag), a single centralized sequencer, permissioned proposers, and a 6/14 MantleSecurityMultisig controlling all protocol upgrades — and the Bybit concentration (holding ~60% of original BIT supply) creates ongoing treasury dependency risk. These factors justify a CAUTIONARY band (not WARNING), and a score of approximately 60: legitimate, operational, audited, no fraud, but with non-trivial centralization and key-person/exchange concentration risks that users should understand before depositing funds.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}