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 · Syscoin
- Sequence
- #3
- Score
- 26 → 26 (0)
- Cluster
- mainnet-beta
- Slot
- 464364645
- Off-chain at
- 2026-11-02T04:41:40.052Z
- Anchored at
- 2026-11-02T04:41:54.000Z
- Block time
- 2026-11-02T04:41:54.000Z
Independent verification
- 1. Database (off-chain)
- 9YdbNfEAe9hjJNSvEcyypZ6x3zK3o59QV2vXKASAQYgg
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1382 chars)
{"actor":"reviewer","artifact_identity":"0fc298d0f810b2c084795927e210f3cc","blocked_count":1,"decided_at":"2026-11-02T04:41:40.000Z","decision":"review","disputed_pct":0.25,"findings_hash":"5w6ZMAMT21WXimFJTxcw8WwuxQRHWp5DqHvbUtQgXUjw","investigation_id":"078f37a7-dac7-42dd-a304-cbd30b11626b","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"omissions":{"material":0,"total":1},"page_content_hash":"1370d3112d335c07a80015b52c9826ad34675446b63a94980fee5698dcc07a9e","page_slug":"syscoin","prev_score":26,"reason":"The core June 2026 exploit narrative (date, 5B SYS, $8.56M, addresses, 568% inflation, recovery, burn, bridge paused) is supported by Rekt and the official postmortem. Weak points are the post-disclosure price-drop timing, the June 18 burn-announcement date (the official postmortem is June 15 and press coverage June 17), unverified June 10-11 return dates, and unchecked 2014 and 2024 claims, several of which sit behind blocked or unfetched sources. No contradiction with current status was found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":12,"sequence_num":3,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}