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_approve · Ronin Bridge
- Sequence
- #3
- Score
- 18 → 52 (+34)
- Cluster
- mainnet-beta
- Slot
- 426699703
- Off-chain at
- 2026-06-15T19:41:32.505Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 8x8Y8ZHLbjYsfkkZcBLFH9d5EbB5f6WMjh93NzPNxpiK
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1775 chars)
{"actor":"judge","decided_at":"2026-06-15T19:41:32.291Z","decision":"review_approve","investigation_id":"f9972424-1a26-4b10-a745-6db7ce736307","new_score":52,"page_slug":"ronin-bridge","prev_score":18,"reason":"The reviewer found zero disputed claims across 19 total findings, with four partial-support results attributable to minor methodological differences (the $625M vs $540M valuation reflects ETH price at discovery vs theft date, not a factual error), an imprecise technical description of the 2024 upgrade root cause, and two editorial aggregations not directly sourced in a single document. No link rot, no stale citations, and no unverifiable claims were detected (summary confidence 0.88). Critically, the calibration assessment confirms both major incidents are attribution type 'b' (suffered): the March 2022 Lazarus Group attack was state-sponsored via social engineering and the August 2024 event was a deployment error front-run by white hats who returned all funds in full. The entity's own conduct — voluntary $150M fundraise to reimburse all victims, validator set expansion, security audits by Verichains and CertiK, and proactive migration to Chainlink CCIP by April 2025 — is inconsistent with a CRITICAL band score of 18. The only legitimate penalty factor is the unrevoked Axie DAO validator access-control lapse, which is a genuine governance failure but not fraud. A score of 52 (CAUTIONARY) correctly reflects the fraud-likelihood semantics in the scoring rubric: the entity was the victim of the largest DeFi hack in history, responded responsibly, and has since materially improved its security posture.","score_delta":34,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}