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 · Solana Mobile
- Sequence
- #4
- Score
- 68 → 68 (0)
- Cluster
- mainnet-beta
- Slot
- 462177966
- Off-chain at
- 2026-10-27T18:48:58.114Z
- Anchored at
- 2026-10-27T18:49:15.000Z
- Block time
- 2026-10-27T18:49:15.000Z
Independent verification
- 1. Database (off-chain)
- 2ejrZvMz4F4N2HmKsM4KfZzV18HEbBZUuQFi1JuXWKEW
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1814 chars)
{"actor":"judge","artifact_identity":"3f29db619fae5f8b0b210fb2728b1131","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T18:48:57.780Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1429,"investigation_id":"eb27435b-d632-45a1-9d0e-a5189d636c6d","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":68,"page_slug":"solana-mobile","prev_score":68,"reason":"Of 8 claims checked, 1 was excluded because its source (Blockworks) blocked the reviewer, which is a coverage limit and not a defect of the page. Of the remaining 7, none were contradicted and 1 could not be verified (claim_findings[6], not_found), giving about 14% disputed. Four claims are only partially supported because details such as the $1,000 launch price, the MKBHD trophy request, Apple's five-year figure and the Seeker-unaffected statement are not in the cited sources (claim_findings[1], [2], [4], [5]). The page also omits the January 2026 SKR token launch, which the reviewer rated a material omission and a high-priority coverage gap. The core Saga overselling and end-of-support accounts are confirmed (claim_findings[0], [3]).","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":7,"sequence_num":4,"severity_override":{"applied":true,"band":"minor","from_band":"minor","reason":"The review reports a material omission (the January 2026 SKR token launch, with its airdrop, staking and token-risk implications) that the page does not mention. The percentage band alone would not capture this, so the page is judged in the minor band with a delta toward the harsher end, not approved."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}