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 · Inertia Protocol
- Sequence
- #3
- Score
- 42 → 42 (0)
- Cluster
- mainnet-beta
- Slot
- 425425632
- Off-chain at
- 2026-06-09T23:16:09.317Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 2V935JeQ4mUooVvhhUAaeTPs5w88yzRHwgNdnynbdvwr
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1188 chars)
{"actor":"judge","decided_at":"2026-06-09T23:16:09.096Z","decision":"review_approve","investigation_id":"d4a4a5ac-1aec-45f3-8f48-bf26ed7247f7","new_score":42,"page_slug":"inertia-protocol","prev_score":42,"reason":"25 of 28 claims were confirmed; the remaining 3 are partially-supported on minor framing issues (claim_findings[8]: irta.io unresponsive at review time; claim_findings[22]: $50 deposit threshold context slightly imprecise; claim_findings[26]: April 25 mainnet date inferred from post publication date rather than explicit text). Zero claims were disputed. The core exploit facts — $152,000 loss, ERC4626 inflation vector, five affected markets, 99.7% supply reduction, Insurance Fund restoration — all corroborated by independent sources. Three high-priority coverage gaps exist (on-chain exploit verification, independent Insurance Fund confirmation, post-exploit protocol status as of June 2026) and should be addressed in a future update, but they indicate expansion opportunities rather than factual errors warranting revision.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}