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 · Heisenberg Guru (HSBG)
- Sequence
- #3
- Score
- 4 → 0 (-15)
- Cluster
- mainnet-beta
- Slot
- 443514277
- Off-chain at
- 2026-08-25T13:18:00.060Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 4vqcQiQQUyrirAGUCRm2e9e4J6tei4gSuPSPAoU5ay7X
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2079 chars)
{"actor":"judge","decided_at":"2026-08-25T13:17:59.702Z","decision":"review_revise","investigation_id":"1f6fe2a8-fed3-4345-8ad3-061d127d7ac3","new_score":0,"page_slug":"heisenberg-guru-hsbg","prev_score":4,"reason":"Most of the page's granular figures — prices, wallet-concentration percentages, and quoted statements for RIVER, RAVE, SIREN, and LAB — were checked against their cited sources and hold up (claim_findings[1], [10]-[16], [19]-[26]). But the review found that the page's central premise — that Heisenberg Guru (HSBG) is the confirmed operator behind a manipulation pattern spanning all six named tokens — is not established by any source consulted (claim_findings[2], [10]; coverage_gaps[0], marked high priority). Reporting on five of the six tokens (RAVE, SIREN, MYX, SKYAI, LAB) attributes the pattern to an unnamed 'unknown market maker,' while HSBG is tied specifically to RIVER through a separate, later bounty naming 'Sion' and 'Chao.' Because this attribution is the page's organizing subject rather than an isolated detail, it registers as only two entries out of thirty-four tracked claims, which understates its practical weight — the disputed-claim percentage (11.8%) is a poor proxy for how central this defect is to the page's identity, and the penalty here is set at the top of the applicable range to reflect that rather than the mechanical percentage alone. Weighing the other direction, the page's own RAVE and SIREN sections already disclose that their specific source articles do not name HSBG, and the page appropriately declines to identify two named LAB individuals as HSBG operators (claim_findings[28]) — both signs of editorial restraint that keep this at a revise rather than a deny. The remaining disputed items are a single recurring one-day date error appearing in three places (claim_findings[18]) and one unsupported token-launch date (claim_findings[34]), both minor and easily corrected.","score_delta":-15,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}