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 · WAYGU CASH
- Sequence
- #2
- Score
- 18 → 18 (0)
- Cluster
- mainnet-beta
- Slot
- 419388811
- Off-chain at
- 2026-05-13T03:26:05.005Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 8kJvUyRhVdemZfv7HeyL3uKbkCMZU1B2Sp7y9VhgZnMQ
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1226 chars)
{"actor":"judge","decided_at":"2026-05-13T03:26:04.695Z","decision":"review_approve","investigation_id":"6e6d83f0-9fb9-4fee-a5dd-a32f291c6c42","new_score":18,"page_slug":"waygu","prev_score":18,"reason":"The review confirmed 27 of 31 claims outright, with 2 partially supported and 1 unverifiable. No claims were disputed. The two partial findings are non-material: claim_findings[21] cites 98.7% vs the Solidus Labs report body's 98.6% (the page sourced the rounded headline from the same organization's own X post), and claim_findings[10] slightly overstates team anonymity by omitting a pseudonymous developer persona the project itself promotes — neither finding undermines the page's core risk characterization. The unverifiable timeline entry (claim_findings[33], the July 1, 2025 listing date) is a secondary estimate that does not affect any substantive conclusion. Three high-priority coverage gaps — holder concentration, liquidity lock status, and mint/freeze authority — are unaddressed but are disclosed by the page itself and represent expansion work, not factual error.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}