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 · Hxro Network
- Sequence
- #5
- Score
- 58 → 53 (-5)
- Cluster
- mainnet-beta
- Slot
- 425212202
- Off-chain at
- 2026-06-08T23:41:51.942Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- EJ3tRP7Lu83aRh9A7ne8xSrC7JPkZzjVn1QJS8SQJtzL
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1451 chars)
{"actor":"judge","decided_at":"2026-06-08T23:41:51.709Z","decision":"review_revise","investigation_id":"c5c72837-af09-4db4-ba3c-27ff8c451ec1","new_score":53,"page_slug":"hxro","prev_score":58,"reason":"Core fundraising, protocol architecture, team background, security audit, and regulatory claims are well-supported by contemporaneous primary sources (claim_findings[0] through claim_findings[5], claim_findings[8] through claim_findings[16], claim_findings[20] through claim_findings[23]). The overall disputed rate of 6.5% is driven by precision and currency issues rather than fabrication. However, three concrete corrections are warranted: claim_findings[19] shows the Coinbase and Kraken exchange listings cannot be confirmed as active trading venues — Kraken explicitly marks HXRO as not currently tradable; claim_findings[17] and claim_findings[18] show market cap, FDV, and daily volume figures that are materially stale relative to current data. Additionally, the review identified a high-priority coverage gap — the January 2025 rebrand of Hxro Network to ODDSFi — that makes all current-state sections of the page substantially outdated. This omission, together with a one-month date error in timeline[4] (disputed) and a dead link in timeline[5] (link_rot), warrants revision before re-approval.","score_delta":-5,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}