Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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 · UPay
View on Solana ↗
Sequence
#6
Score
53 → 53 (0)
Cluster
mainnet-beta
Slot
461974848
Off-chain at
2026-10-27T06:49:02.542Z
Anchored at
2026-10-27T06:49:17.000Z
Block time
2026-10-27T06:49:17.000Z

Independent verification

1. Database (off-chain)
GbrvvGMjqYfJCBSbAkJ5n7LTG6rXzunriNQB5X7daLGr
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1590 chars)
{"actor":"judge","artifact_identity":"4bab9560665dd22a5dd3ffe6afea70bf","band_override":null,"blocked_count":2,"decided_at":"2026-10-27T06:49:02.203Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1667,"investigation_id":"3cc0429e-ec7e-404f-9e16-fb08e210271c","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":53,"page_slug":"upay","prev_score":53,"reason":"The core of the page holds up: the October 2 ZachXBT allegation, the September 9 OFAC designation of Xinbi, the UK action and the statement that no evidence confirms a UPay card are all corroborated (claim_findings[0], [4], [6], [7]). Of 8 findings, 2 could not be checked because the source blocked the reviewer and were left out of the count. Of the remaining 6, 1 was unverifiable, so the disputed share is about 17%. The 'Dubai-based' description is not supported by any readable source (claim_findings[1]), and the '52 TRON addresses' figure was not found in the fetched sources, which mention 47 wallets (claim_findings[5]). A high-priority coverage gap on UPay's corporate identity, licensing and issuing partner also keeps this at a minor revision rather than an approval. About 25% of findings could not be checked because the source refused access, which limits this review but is not a defect of the page.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":6,"sequence_num":6,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}