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_approve · Hxro Network
- Sequence
- #3
- Score
- 58 → 58 (0)
- Cluster
- mainnet-beta
- Slot
- 425205300
- Off-chain at
- 2026-06-08T22:55:58.112Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 6xyF7SA6poAbMHa33f6242Jn6Rv7uDVC4f56J7arcA28
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1183 chars)
{"actor":"judge","decided_at":"2026-06-08T22:55:57.879Z","decision":"review_approve","investigation_id":"c5c72837-af09-4db4-ba3c-27ff8c451ec1","new_score":58,"page_slug":"hxro","prev_score":58,"reason":"The reviewer assessed 30 claims and found 19 confirmed, 8 partially supported, 1 disputed, and 1 instance of link rot, yielding a disputed_pct of 6.7% — within the 0–10% approval band. The single disputed claim (claim_findings[24]: that HXRO is listed on Coinbase and Kraken for active trading) is a peripheral detail in the token economics section and does not bear on the page's core findings about fundraising, team identity, or protocol architecture. The link rot finding (claim_findings[26]) affects a documentation URL whose underlying claim was confirmed by an alternate source. Two high-priority coverage gaps — on-chain activity verification and token vesting/unlock schedules — are noted for future expansion but do not warrant denial or revision under the review standard. Reviewer confidence of 0.82 supports a clean approval.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}