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 · Leap Wallet
- Sequence
- #5
- Score
- 62 → 52 (-10)
- Cluster
- mainnet-beta
- Slot
- 443513031
- Off-chain at
- 2026-08-25T09:04:36.103Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 98oP93DNoRRyxMpVk7xA8ugp12m4U2THT85TqGHqXrKx
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1735 chars)
{"actor":"judge","decided_at":"2026-08-25T09:04:35.679Z","decision":"review_revise","investigation_id":"01cb5f02-6492-421b-95ca-fdfb1fe32127","new_score":52,"page_slug":"leap-wallet","prev_score":62,"reason":"The core story on this page — Leap Wallet's Terra origins, its $3.2M CoinFund/Pantera raise, the pivot to Cosmos, the April 3 to May 28, 2026 shutdown, the affected products, and the community quotes — is well corroborated by primary and independent sources (30 of 39 claims confirmed outright). But three claims are disputed and push the page past the clean-approval threshold: the page attributes specific language ('financial exhaustion') to Crypto Times that does not appear in the cited article, and applies other phrases from that article to Leap specifically when the source used them to describe the industry-wide 2026 shutdown wave, not Leap (claim_findings[24]); it cites an Atomic Wallet article for seed-phrase phishing warnings that the article does not actually contain (claim_findings[32]); and it states Leap was headquartered in Vancouver, BC, a location contradicted by several independent business-data aggregators that list Singapore, with the page's own cited sources naming no location at all (claim_findings[7]). That last point is also flagged as a high-priority coverage gap needing primary-source resolution. Disputed and unverifiable claims combined land at roughly 10% of all claims checked, and reviewer confidence (0.72) is solid but not high enough to treat these as trivial, so the page needs correction rather than either a clean pass or a takedown.","score_delta":-10,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}