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 · Jupiter Perps
- Sequence
- #5
- Score
- 66 → 54 (-12)
- Cluster
- mainnet-beta
- Slot
- 425204357
- Off-chain at
- 2026-06-08T22:49:43.762Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- Btsizhna7zDSCUWJDxpNLT4vszxVGgPEFc9PtmnnYp2n
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1414 chars)
{"actor":"judge","decided_at":"2026-06-08T22:49:43.590Z","decision":"review_revise","investigation_id":"6539e14c-8eb6-4307-8cf9-bd28d784c81c","new_score":54,"page_slug":"jupiter-perps","prev_score":66,"reason":"The investigation is broadly accurate: 18 of 27 claims are fully confirmed by credible sources, and the five partially-supported findings are minor framing imprecisions. However, one claim is directly disputed by official sources: claim_findings[19] states the maintenance margin threshold is 0.625% of position size (margin ratio below 6.25%), while multiple sources citing Jupiter's own documentation put this figure at 0.2% — a material discrepancy in a section readers may rely on for risk assessment. The dependent claim at claim_findings[28] (0.4% adverse move triggers full liquidation at 250x) is therefore also unverifiable. Additionally, the cited OtterSec audit PDF URL (hub.jup.ag) is confirmed dead with link rot, and two high-priority coverage gaps remain unaddressed: the on-chain program upgrade authority status and any regulatory or jurisdictional exposure analysis. Meow's wBTC co-founding claim (claim_findings[22]) is overstated relative to what the primary cited source actually says and should be softened to reflect what is verifiable.","score_delta":-12,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}