Skip to main content
AVOID.NET
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 · Levana Perps
View on Solana ↗
Sequence
#2
Score
32 → 32 (0)
Cluster
mainnet-beta
Slot
443520487
Off-chain at
2026-08-26T11:21:56.507Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
42UneVUvF7cXjxhoJXAU7UzMdwCe9jeoWq2ULCncxwQd
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1249 chars)
{"actor":"reviewer","decided_at":"2026-08-26T11:21:56.432Z","decision":"review","investigation_id":"2b7bf4c3-bd49-4686-972d-166f46d25944","new_score":32,"page_slug":"levana-perps","prev_score":32,"reason":"The page's core narrative about the December 2023 Levana Perps exploit — the $1.14M loss figure, ~10% LP impact, 13-day oracle-manipulation attack vector on Osmosis, concurrent DDoS, and the 2025 Rujira/RUJI token migration timeline — is well corroborated by multiple independent sources and correctly attributes the exploit to oracle/chain-layer conditions rather than a Levana smart-contract bug. It also correctly reports LP compensation, avoiding the remediation-understatement pattern seen elsewhere. The main issues found are one dead citation (a CoinMarketCap AI page used for a specific Gate.io trading-halt claim), two claims that slightly conflate dates/timing, and — most significantly — a completely empty section body across all six sections that omits a material, well-documented 2026 development: Levana's exit from the Rujira Alliance and discontinuation of its isolated Perps product.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}