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_approve · $VLAD
- Sequence
- #7
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 464253335
- Off-chain at
- 2026-11-01T22:04:05.177Z
- Anchored at
- 2026-11-01T22:04:25.000Z
- Block time
- 2026-11-01T22:04:25.000Z
Independent verification
- 1. Database (off-chain)
- DrkGvdmJ3BBg8wZ4oYG2WdKvNzyPrPNrDn1oiUYA1DC8
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1796 chars)
{"actor":"judge","artifact_identity":"cde3a2ab64b5fb332aac99a329ebbf5c","band_override":null,"decided_at":"2026-11-01T22:04:04.897Z","decision":"review_approve","delist_requested":false,"disputed_pct":0.0909,"investigation_id":"3035892c-72b1-4dae-a040-3375f8404fda","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"vlad","prev_score":0,"reason":"Of 11 claim findings, 1 is disputed and none are unverifiable, giving about 9% disputed, which falls in the approve band. The core account of the July 23 hijack, Robinhood's confirmation, the 175,000-view figure, the 650 ETH estimate and Tenev's July 28 statement is confirmed by Tier 1-2 sources (claim_findings[0,1,3,4]). The disputed item, claim_findings[7], is the page's statement that the $22 million volume figure was independently corroborated by The Block and Cointelegraph; neither article contains it, though the figure itself is supported by The Defiant (claim_findings[6]). That sentence should be corrected, and the partially supported details (the PonsLaunchFactory name, the 'about two hours' duration, and the low-tier sourcing for the $18.43 million rug-pull claim) should be tightened, but they do not undermine the page overall.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":7,"severity_override":{"applied":false,"band":null,"from_band":"approve","reason":"Not required by the rules: the only omission (claim-free copycat VLAD pools) is minor, subject_status shows the token still trading with no shutdown or sanction contradicting the page, and no high-priority coverage gap is open."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}