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
#3
Score
38 → 38 (0)
Cluster
mainnet-beta
Slot
424157088
Off-chain at
2026-06-04T02:54:27.897Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
FJKXBGp596avALufkimmSLdcMdGgpQ9iuY4dMQ9S8aJi
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1268 chars)
{"actor":"judge","decided_at":"2026-06-04T02:54:27.716Z","decision":"review_approve","investigation_id":"276bd4a1-f6d6-42f2-834c-b153f3b62ae0","new_score":38,"page_slug":"sushiswap-routeprocessor","prev_score":38,"reason":"The reviewer assessed 25 claims and found 23 confirmed, 1 partially supported, and 0 disputed, yielding a disputed_pct of 4% — well within the approve band. The one partially supported finding (claim_findings[7]: HYDN rescue amount stated as $750k while HYDN's own blog says $600k) is resolved by the page's reliance on the official SushiSwap post-mortem, a Tier 1 source that gives the higher consolidated cross-chain figure. The single unverifiable entry (claim_findings[24]: April 25 claim portal launch date) depends on an X/Twitter URL that cannot be fetched but is structurally consistent with the date. No link rot, no stale citations, and no core allegations are contradicted. The one high-priority coverage gap — whether Group 2 victims were actually made whole after April 2023 — represents a meaningful expansion opportunity but does not undermine the accuracy of what is currently published.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}