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_revise · Cork Protocol
- Sequence
- #3
- Score
- 34 → 22 (-12)
- Cluster
- mainnet-beta
- Slot
- 425023538
- Off-chain at
- 2026-06-08T02:49:36.249Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 77rPsg9SWNfMQyctsWYYeH8gnEaTQYRojvFaBeHXNeVa
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1365 chars)
{"actor":"judge","decided_at":"2026-06-08T02:49:36.066Z","decision":"review_revise","investigation_id":"f8750343-b24f-46fb-a1a2-526e01032f36","new_score":22,"page_slug":"cork-protocol","prev_score":34,"reason":"The page's core exploit facts — attack mechanics, vulnerability descriptions, attacker wallet addresses, Tornado Cash laundering amounts, and audit scope failures — are well-sourced and confirmed across multiple independent outlets. However, claim_findings[22] and claim_findings[24] identify a material conflation in the funding history: the $5.5 million figure and Road Capital and BitGo's participation are incorrectly attributed to the September 2024 round, when those details belong exclusively to the January 2026 round; the September 2024 round's amount was never publicly disclosed. Additionally, claim_findings[25] and claim_findings[26] record that the Cork Phoenix mainnet launch date is stated as January 19, 2026, while multiple sources including The Block cite January 8, 2026. These errors appear in both the Funding section and the timeline, requiring correction. One high-priority coverage gap — the unresolved status of user compensation — is also noted and should be addressed in a revision.","score_delta":-12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}