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 · Light Protocol
- Sequence
- #3
- Score
- 74 → 69 (-5)
- Cluster
- mainnet-beta
- Slot
- 424057538
- Off-chain at
- 2026-06-03T15:53:06.346Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- DMF7oNBaVfrxZh69TDyN4mNiKhEcpBGwn59KZHyMMxkg
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1164 chars)
{"actor":"judge","decided_at":"2026-06-03T15:53:06.089Z","decision":"review_revise","investigation_id":"fa89a22c-e13a-4966-93ed-efd15257403c","new_score":69,"page_slug":"light-protocol","prev_score":74,"reason":"The page is broadly accurate and well-sourced across 23 checked claims, with 15 confirmed and no evidence of fraud, regulatory action, or fund loss. However, two related factual errors require correction: claim_findings[20] shows Breakpoint 2024 is dated October 2024 in the timeline but was definitively held September 20-21, 2024, confirmed by a Tier 1 source; and claim_findings[2] and claim_findings[19] establish that the June 2024 launch was devnet-only, not mainnet plus devnet as the page states in both the overview section and the timeline — mainnet went live at Breakpoint in September 2024. The reviewer flagged the devnet/mainnet distinction as a high-priority coverage gap. All core claims about funding, audit coverage, bug bounty details, and absence of misconduct are independently confirmed.","score_delta":-5,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}