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 · Injective Protocol
- Sequence
- #3
- Score
- 62 → 55 (-7)
- Cluster
- mainnet-beta
- Slot
- 425195488
- Off-chain at
- 2026-06-08T21:50:30.932Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- HGvX3jbXSGSvKqEaAJeNVvPcwx821UXpYahBr5WBWZEr
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1371 chars)
{"actor":"judge","decided_at":"2026-06-08T21:50:30.645Z","decision":"review_revise","investigation_id":"11951e44-8e44-429d-bcea-351b9c671b7d","new_score":55,"page_slug":"injective-protocol","prev_score":62,"reason":"The review confirmed 24 of 34 claims outright, with zero actively disputed claims and a reviewer-computed disputed_pct of 8.8%. However, a high-priority coverage gap — the complete omission of Injective's August 2022 $40 million Series A led by Jump Crypto and Brevan Howard, and the mislabeling of the April 2021 private token sale as a 'Series A' (claim_findings[10]) — materially understates total capital raised and warrants revision before this finding can be fully approved. Two dead citation links (claim_findings[16] and claim_findings[18]: Immunefi bug bounty page and a CoinTelegraph article) affect the high-severity bug bounty section and should be replaced. The remaining partially-supported items are minor: a 6-day date discrepancy in the ecosystem fund timeline (claim_findings[33]), a 1-day off-by-one on the Bitnomial futures launch date (claim_findings[34]), and an unverifiable code-commit figure sourced from AI-generated summaries (claim_findings[27]). No core allegations are contradicted.","score_delta":-7,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}