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 V1
- Sequence
- #3
- Score
- 10 → 0 (-10)
- Cluster
- mainnet-beta
- Slot
- 465082918
- Off-chain at
- 2026-11-03T23:25:57.809Z
- Anchored at
- 2026-11-03T23:26:27.000Z
- Block time
- 2026-11-03T23:26:27.000Z
Independent verification
- 1. Database (off-chain)
- GaydrjyfXHhNCe2ciZsRR4zn3HGR7u57YRxWkS2tBJUz
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1851 chars)
{"actor":"judge","artifact_identity":"0eae4b321c053b65b977813af0431d13","band_override":null,"decided_at":"2026-11-03T23:25:57.497Z","decision":"review_revise","delist_requested":false,"disputed_pct":0,"investigation_id":"d46de3f5-5b77-4b7f-bab5-692907d54b7d","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":0,"page_slug":"cork-v1","prev_score":10,"reason":"The core exploit facts (date, time, amount, wstETH to ETH conversion, Tornado Cash laundering) were confirmed, and no claim was disputed outright. The page does contradict the project's own latest status. claim_findings[3] is stale: it says funds are locked with no withdrawal timeline, but Cork reported over $21 million withdrawn from the four unaffected markets. omission_findings[0] reports this as a material omission. claim_findings[2] (the three-auditor scope exclusion) rests largely on Sherlock's contested account, and claim_findings[1] merges events from different dates. A modest penalty and a banner apply until the page is corrected.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":-10,"sequence_num":3,"severity_override":{"applied":true,"band":"minor","from_band":"approve","reason":"Claim findings alone give 0% disputed or unverifiable (no finding is disputed or unverifiable; 2 confirmed, 3 partially supported, 1 stale). However, the review reports a material omission (omission_findings[0]: four of five markets unaffected and over $21M withdrawn) and subject_status.contradicts_page is true. The page implies depositors remain locked out. Escalated to the minor band, not higher, because the core exploit facts hold and the reviewer's confidence is only 0.55."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}