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 · PayPal USD (PYUSD)
- Sequence
- #3
- Score
- 68 → 53 (-15)
- Cluster
- mainnet-beta
- Slot
- 443524016
- Off-chain at
- 2026-08-27T05:29:55.969Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 6rx5rAY7uVs1WyG9ZAKJUP5bHFJQAsNy2SFuSBedAhRz
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2450 chars)
{"actor":"judge","decided_at":"2026-08-27T05:29:17.192Z","decision":"review_revise","investigation_id":"de455f07-352d-4ec0-997e-17c5b0e301c9","new_score":53,"page_slug":"paypal-usd","prev_score":68,"reason":"Computed literally from the reviewer's own verdicts (7 disputed + 0 unverifiable out of 32 claims), disputed_pct is 21.9%, which places this page in the 10-30% band: review_revise, delta -5 to -15, no status change. This is a band-maximum case: the delta is set to -15 because several of the 7 disputed claims are more than trivial date slips -- claim_findings[17] disputes a 'third-largest stablecoin' ranking that broader market-cap data contradicts, and claim_findings[20] misdates a corporate reorganization by a full quarter, alongside four timeline entries (claim_findings[28]-[31]) that consistently land on the first of a month when independent reporting places the true event later. This figure and band, however, do not capture the page's most serious problem. claim_findings[0], [1], and [5] show the page's central claim about who regulates PYUSD's issuer (NYDFS-chartered Paxos Trust Company, LLC) is stale, not disputed -- Paxos converted to a federally chartered OCC national trust on December 12, 2025, and the page's own cited Paxos sources, archived after that date, already reflect the correct status. Because the disputed_pct formula excludes stale findings from its numerator by design, this material misstatement of a regulated issuer's charter and supervisor contributes nothing to the score driving this verdict. The band table has no field that can express that gap: banner and status_change are fixed to the disputed_pct range actually reached (10-30%), and this rationale is the mechanism for surfacing the limitation rather than a change to those fields. The page should be revised with priority given to correcting the issuer's charter/regulator status, even though the schema does not escalate banner or status_change for it at this disputed_pct level. On the favorable side, the review found no unsupported adverse allegations: the BUSD/NYDFS enforcement history, the freeze/wipe centralization risk, and the SEC subpoena are all properly sourced and hedged, and the closed SEC inquiry is described accurately as a closure rather than exaggerated in either direction.","score_delta":-15,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}