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 · SUNRAY·FINANCE
- Sequence
- #4
- Score
- 44 → 44 (0)
- Cluster
- mainnet-beta
- Slot
- 464348648
- Off-chain at
- 2026-11-02T03:44:35.345Z
- Anchored at
- 2026-11-02T03:44:44.000Z
- Block time
- 2026-11-02T03:44:44.000Z
Independent verification
- 1. Database (off-chain)
- 9ScuLWAbFw4vSZisEYd9M9xQNmBYkL84mRwWxNHVEdLj
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1461 chars)
{"actor":"judge","artifact_identity":"3cdbe0482538b32a517ca562190fb3fa","band_override":null,"decided_at":"2026-11-02T03:44:35.085Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2143,"investigation_id":"82a14206-d76d-4f7a-9032-b7a29cc18b54","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":44,"page_slug":"sunrayfinance","prev_score":44,"reason":"The core exploit facts (October 30, 2024 date, contract upgrade, SUN minting, about $2.1M USDT swapped, about $560K bot profit) were confirmed by several outlets (claim_findings[0], [1], [5]). Three of 14 claims (21%) could not be verified: the exploited contract address (claim_findings[3]), the exact 2024-11-30 website-offline date (claim_findings[10]) and the ZachXBT flag (claim_findings[11]). Other claims are only partly supported: the 'no public notification' sentence conflicts with an October 30 X post and with the page's own team-response section (claim_findings[7]), and the 'denied insider involvement' and 'mid-2025 offline' statements lack backing (claim_findings[4], [12]). The reviewer flagged a high-priority gap in on-chain verification, which fits a minor-issues revision rather than approval.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}