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_approve · SushiSwap RouteProcessor Exploit
View on Solana ↗
Sequence
#5
Score
38 → 54 (+16)
Cluster
mainnet-beta
Slot
426514683
Off-chain at
2026-06-14T23:16:08.453Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
7hwu4Pez79swqKFxPf7u6B6C778Loy6n3p89mXUCcMsv
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1415 chars)
{"actor":"judge","decided_at":"2026-06-14T23:16:08.331Z","decision":"review_approve","investigation_id":"276bd4a1-f6d6-42f2-834c-b153f3b62ae0","new_score":54,"page_slug":"sushiswap-routeprocessor","prev_score":38,"reason":"This is a severity-calibration adjudication: all six claim_findings were confirmed supported (0% disputed), and page content is accurate. The review establishes that the current score of 38 (WARNING band) is miscalibrated because the incident was caused by protocol negligence — not fraud — and has been substantively resolved: SushiSwap published a public post-mortem, coordinated a whitehat rescue (claim_findings[0]), committed to full victim compensation with a live claim portal (claim_findings[1]), paid a $200K bounty to HYDN, and documented procedural improvements including mandatory pre-deployment audits and pausability (claim_findings[5]). WARNING-band semantics require elevated ongoing fraud risk or an unresolved severe incident; neither condition holds. The CAUTIONARY band (score 54) correctly reflects SushiSwap's pattern of four security incidents and the ongoing SEC subpoena (claim_findings[4]) while distinguishing negligence from fraud. A positive delta of +16 moves the score from 38 to 54, aligning it with the correct band.","score_delta":16,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}