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 · Plasma (XPL)
- Sequence
- #4
- Score
- 60 → 60 (0)
- Cluster
- mainnet-beta
- Slot
- 462179258
- Off-chain at
- 2026-10-27T18:53:37.825Z
- Anchored at
- 2026-10-27T18:53:46.000Z
- Block time
- 2026-10-27T18:53:46.000Z
Independent verification
- 1. Database (off-chain)
- 6GykabhJzQRVEaZLUAM36TKsxwDAjn1bacMHo4mxNvrZ
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1907 chars)
{"actor":"judge","artifact_identity":"78c88157cc5bf9ebdf4fe57f906231bb","band_override":null,"blocked_count":2,"decided_at":"2026-10-27T18:53:37.574Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2222,"investigation_id":"27ce12e3-0506-455c-a905-b45390291ee7","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":60,"page_slug":"plasma","prev_score":60,"reason":"Of 11 claim findings, 2 were set aside because the source refused the reviewer (source_blocked), leaving 9. Two of those, the mid-August 2026 DeFiLlama figures (claim_findings[8] and [9]), could not be verified, which gives a disputed share of about 22%. The core crash, tokenomics and CoinDesk claims were confirmed by Tier 1 sources. Two backer attributions are not in the cited CoinDesk article (claim_findings[0] and [1]), and the page omits that the team and investor cliff passed on 2026-09-25 (omission_findings[0]) and still describes the US purchaser unlock as upcoming. A high-priority gap also remains for developments after November 2025. The reviewer's confidence was moderate (0.55), so the penalty sits in the minor band rather than higher.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":9,"sequence_num":4,"severity_override":{"applied":false,"band":null,"from_band":"minor","reason":"The material omission (team and investor one-year cliff passed 2026-09-25) is a stale forward-looking statement. The reviewer confirmed the underlying schedule against the Tier 1 tokenomics docs, and no shutdown, exploit or sanction was found (subject_status.contradicts_page is false). That does not justify an investigation-level band, but it is reflected in the upper part of the minor band."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}