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 · Carrot Protocol
- Sequence
- #1
- Score
- 32 → 32 (0)
- Cluster
- mainnet-beta
- Slot
- 419337708
- Off-chain at
- 2026-05-12T21:44:41.201Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 9Xh18pgnGMS7Mj16FD6fypoKa1JMQGShoYFgvJGg1igx
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1333 chars)
{"actor":"reviewer","decided_at":"2026-05-12T21:44:41.095Z","decision":"review","investigation_id":"66deb8ba-9978-4277-ac06-a4590184fe62","new_score":32,"page_slug":"carrot-protocol","prev_score":32,"reason":"The Carrot Protocol investigation page is substantially accurate and well-sourced. The core narrative — that Carrot shut down as a downstream casualty of the April 1, 2026 Drift Protocol exploit — is confirmed by multiple independent sources. The most significant factual error is the characterization of Drift Protocol as 'the largest DeFi lending platform on Solana' when it is consistently described by authoritative sources (Chainalysis, QuillAudits, Drift's own documentation) as a perpetual futures DEX. Secondary issues include a one-day discrepancy in the multisig migration date (March 26 vs. March 27), a transaction count discrepancy (31 vs. 33), a disputed claim that Carrot 'operated for more than two years' given a 2024 founding, and minor imprecision in the April 2026 monthly incident count (page says 25, most authoritative sources say 28-30). The Drift TVL, exploit amount, asset breakdown, DPRK attribution, and Carrot wind-down mechanics are all well-supported.","score_delta":0,"sequence_num":1,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}