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 · Serenity Shield
- Sequence
- #4
- Score
- 50 → 50 (0)
- Cluster
- mainnet-beta
- Slot
- 464370944
- Off-chain at
- 2026-11-02T05:04:07.021Z
- Anchored at
- 2026-11-02T05:04:27.000Z
- Block time
- 2026-11-02T05:04:27.000Z
Independent verification
- 1. Database (off-chain)
- C3cFKkHTb31JQEx1mNphaUPZG4S2SbtgfRMV9Ymx7qUi
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2031 chars)
{"actor":"judge","artifact_identity":"985d42576bb658d453895b8eeb423a86","band_override":null,"blocked_count":1,"decided_at":"2026-11-02T05:04:06.807Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.375,"investigation_id":"43f5040f-ae85-41db-951f-41d62945cded","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":50,"page_slug":"serenity-shield","prev_score":50,"reason":"The core incident is supported by the sources the reviewer could read: the February 2024 wallet compromise, about $586,000 realized, the 95%+ price collapse, the 15% bounty offer and the ZachXBT linkage (claim_findings[0], [7], [4]). However, 3 of 8 checkable claims could not be verified (claim_findings[1], [2], [5]), and 2 more were only partly supported (claim_findings[4], [6]). The cited Altcoin Buzz reissue article is dead and backs several claims (claim_findings[3]). The page also gives two conflicting times for the exploit, 9:11 AM and 2:26 PM UTC (claim_findings[1], [2]). It presents the $5.6M figure without saying it is a nominal value, and it omits the reported February 2026 rebrand and token swap to Real World Services (omission_findings[0]). Reviewer confidence is moderate and one source for the rebrand is uncorroborated, so the penalty sits in the middle of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":8,"sequence_num":4,"severity_override":{"applied":true,"band":"significant","from_band":"significant","reason":"The review reports a material omission (the February 2026 rebrand and 1:1 swap of SERSH to Real World Services) and marks subject_status.contradicts_page as true. The percentage band is already significant, so the override confirms that band and does not move it further. It is held at significant rather than deny because the rebrand rests on a single source."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}