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
- 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. - 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.
- 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 · SushiSwap RouteProcessor Exploit
- Sequence
- #4
- Score
- 38 → 38 (0)
- Cluster
- mainnet-beta
- Slot
- 426514680
- Off-chain at
- 2026-06-14T23:16:08.378Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- GFAJMv47NDdBm6zcztm4cqrSbmpjeBE9DSuxpGnseADU
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1828 chars)
{"actor":"reviewer","decided_at":"2026-06-14T23:16:08.331Z","decision":"review","investigation_id":"276bd4a1-f6d6-42f2-834c-b153f3b62ae0","new_score":38,"page_slug":"sushiswap-routeprocessor","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. The SushiSwap RouteProcessor2 page documents a confirmed April 2023 DeFi security incident in which SushiSwap deployed an unaudited router contract lacking input validation, resulting in ~$3.3M in user losses. This is own-negligence attribution — the protocol made a security mistake — but the entity is not fraudulent. SushiSwap responded with public transparency (Jared Grey's immediate public statement), whitehat coordination with HYDN, a structured two-tier compensation program with a live claim portal (April 25, 2023), a $200K bounty paid to HYDN, and documented procedural improvements including pausability and pre-deployment audits. The current score of 38 (WARNING band) is over-penalized because the band semantics require either elevated ongoing fraud risk or an unresolved severe incident; the incident was resolved and the protocol demonstrated responsible disclosure and remediation. Under the post-policy band semantics, CAUTIONARY (50-69) is the correct designation: SushiSwap is a legitimate, operating DeFi protocol with material caveats including a history of four security incidents and an ongoing SEC subpoena. A score of 54 reflects the seriousness of the negligence (unaudited production deployment, ~$3.3M loss, pattern of prior incidents) while correctly distinguishing security failure from fraud.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}