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 · UPay
- Sequence
- #7
- Score
- 53 → 53 (0)
- Cluster
- mainnet-beta
- Slot
- 462359395
- Off-chain at
- 2026-10-28T05:32:57.527Z
- Anchored at
- 2026-10-28T05:33:22.000Z
- Block time
- 2026-10-28T05:33:22.000Z
Independent verification
- 1. Database (off-chain)
- BvapkamDSpX7g9yNU3s1DYJKjv8g8kFGevJCpAKZKC18
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2199 chars)
{"actor":"reviewer","artifact_identity":"07af80eec8892b0a584634d40a5fc2da","decided_at":"2026-10-28T05:32:57.365Z","decision":"review","disputed_pct":0.0625,"findings_hash":"EZrStpG1Wr2EvUwr1tGRVDEtqknoD8ZUKUhrUPmT222m","investigation_id":"3cc0429e-ec7e-404f-9e16-fb08e210271c","mode":"findings_only","new_score":53,"page_content_hash":"7a4b1946983e772cf8e9b9c59108ec6ab8d53ec3951f5b9f7740742d52db31b6","page_slug":"upay","prev_score":53,"reason":"The page's core claims are well supported by independently verifiable sources: the OFAC/Treasury sanctions details (date, legal basis, designated entities, 52 TRON addresses, $24B Treasury-attributed figure, UK precursor action) all check out against primary government sources, and the ZachXBT/UPay allegation and Owen Yang's reported response are corroborated by multiple independent crypto-news outlets, even though the primary cited CryptoTimes article itself could not be directly fetched (403). The page is appropriately careful to frame the Xinbi/UPay relationship as an unconfirmed allegation rather than a finding, which matches the state of public evidence as of this review. The most substantive issue found is that the page characterizes the DOJ's Scam Center Strike Force action as a 'seizure of more than $52 million,' when DOJ's own language describes that figure as 'restrained,' with only about $12 million actually seized outright — this overstatement appears identically in the prose section and the timeline event and should be corrected in both places (defect_group upay-doj-seizure-characterization). A secondary, minor issue is an apparent one-day discrepancy between the page's 'same day' reporting claim and the actual publication dates of its own cited sources. Coverage gaps include the absence of any on-chain tracing to directly test the central allegation, and no mention of UPay's independent complaint/reputation history.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":7,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}