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 · USX
- Sequence
- #3
- Score
- 62 → 52 (-10)
- Cluster
- mainnet-beta
- Slot
- 443525223
- Off-chain at
- 2026-08-27T10:27:45.333Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 7qoU1BndwdJodyuzsJnUeqRWuVum7bzPMLFGygjVQE55
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1834 chars)
{"actor":"judge","decided_at":"2026-08-27T10:27:44.730Z","decision":"review_revise","investigation_id":"866bcf20-5167-4191-81dd-cfcf0b017cde","new_score":52,"page_slug":"usx","prev_score":62,"reason":"Independent review of 54 factual claims on this page found none disputed by contradicting outside evidence -- the core narrative (Solstice/USX identity, the September 2025 launch, leadership bios, and the December 2025 depeg-and-recovery) is well corroborated by multiple independent outlets. The computed disputed_pct of 18.5% is made up entirely of claims the reviewer could not confirm either way, and a large share of those trace back to the reviewer being blocked from Solstice's own documentation site or hitting dead news links, not to the page being shown wrong (claim_findings[16], [30], [31], [23]). That said, the review did surface two real, page-level problems: the page gives two different answers for what backs USX, USDC/USDT in the summary versus USDC/USDG in the Token Mechanics section (claim_findings[2], [14]), and it states a third-party attestation 'confirmed' collateralization above 100% when its own cited source says an attestation was only requested (claim_findings[26]). Combined with market-cap and rank figures presented as current that had moved substantially by the time of review (claim_findings[6], [51]) and a flagged high-priority gap around on-chain holder/whale analysis of the depeg, this falls short of a clean approval but does not rise to a serious-issues or failing outcome; disputed_pct already places the page in the revise band on its own, so the high-priority coverage gap reinforces that placement rather than pushing it into a harsher one.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}