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 · Mori Finance
- Sequence
- #4
- Score
- 50 → 50 (0)
- Cluster
- mainnet-beta
- Slot
- 462179081
- Off-chain at
- 2026-10-27T18:53:03.623Z
- Anchored at
- 2026-10-27T18:53:09.000Z
- Block time
- 2026-10-27T18:53:09.000Z
Independent verification
- 1. Database (off-chain)
- FyogG1kWQ2z2mS4dAbnDNvmDjZ95uL7QFU1K7PqigG45
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1526 chars)
{"actor":"judge","artifact_identity":"2b46757a50ec680105820bf14907397c","band_override":null,"blocked_count":3,"decided_at":"2026-10-27T18:53:03.387Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1429,"investigation_id":"e4dbe003-3223-4cf1-802d-54feb6701458","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":50,"page_slug":"mori-finance","prev_score":50,"reason":"Of 10 claim findings, 3 could not be read because the source blocked the reviewer and are left out of the calculation. Of the remaining 7, one (claim_findings[6], the xMORI fee-share mechanics) was not found in the cited GitBook page, giving about 14% disputed or unverifiable. Separately, the first-sale duration (claim_findings[0] and [9]) says under two minutes where Holder.io says under five, and the 500-transaction testnet figure (claim_findings[8]) is not in any readable source. Sale dates, amounts and tokenomics figures were confirmed, no shutdown, exploit or omission was found, and the reviewer's confidence is low (0.45), so the penalty is kept small. The 30% blocked share and the high-priority gaps on primary-source verification and on-chain analysis limit how much the review could check, and they are not defects of the page.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":7,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}