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 · GMX V1 Perps
- Sequence
- #4
- Score
- 50 → 50 (0)
- Cluster
- mainnet-beta
- Slot
- 462187393
- Off-chain at
- 2026-10-27T19:22:04.653Z
- Anchored at
- 2026-10-27T19:22:37.000Z
- Block time
- 2026-10-27T19:22:37.000Z
Independent verification
- 1. Database (off-chain)
- 7pJCSfhZwJXy8JH7XrN6zutNY5XnToh2Qp2xh16eUPH4
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2006 chars)
{"actor":"judge","artifact_identity":"60392b4c16ad3a37500ed48835564737","band_override":null,"decided_at":"2026-10-27T19:22:04.339Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.0909,"investigation_id":"8429673a-c5b0-46af-a885-ca3107e51347","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":50,"page_slug":"gmx-v1-perps","prev_score":50,"reason":"The core account holds up. The July 2025 reentrancy exploit of about $42M, the partial return of funds, the September 2022 AVAX manipulation and V1's shutdown are confirmed (claim_findings[0], [3], [4]). Claim-level disputes are low, but the page omits the August 2025 compensation plan for affected GLP holders and still tells them to watch for a recovery pathway (claim_findings[10], omission_findings[0]). The page also leaves the ~$4.2M bounty unreconciled with the $5M retained (claim_findings[1], [2]) and presents an inference about prior audits as Halborn's statement (claim_findings[5]). These are correctable and do not undermine the main account, so a minor revision is appropriate.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"severity_override":{"applied":true,"band":"minor","from_band":"approve","reason":"Counting claim_findings directly, 1 of 11 is unverifiable (not_found) and none is disputed, giving about 9%, which falls in the approve band. The review also reports a material omission: the August 2025 GMX compensation plan (about $44M in GLV tokens) is missing, and claim_findings[10] is stale because the page tells GLP holders to wait for a recovery pathway that was already announced. Escalated one band to minor. The subject is not newly shut down or contradicted (contradicts_page is false), and the omission rests on a single Tier 3 source, so significant is not warranted."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}