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 · Pike Finance
- Sequence
- #2
- Score
- 28 → 28 (0)
- Cluster
- mainnet-beta
- Slot
- 424291258
- Off-chain at
- 2026-06-04T17:44:51.714Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 9oJcAoVtypxEGQ76W7dNAVBq7RMAJXeaS3eJrE3nbTD2
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (972 chars)
{"actor":"reviewer","decided_at":"2026-06-04T17:44:51.541Z","decision":"review","investigation_id":"b1f3fb25-5fcd-4377-b433-917b184e949e","new_score":28,"page_slug":"pike-finance","prev_score":28,"reason":"The Pike Finance investigation page is well-sourced and accurate on all material claims. Core facts — exploit dates, token amounts, fund movements, vulnerability mechanisms, attacker addresses, and the CCTP mischaracterization correction — are independently confirmed by multiple tier-1 security research firms. Two minor partial-support findings relate to paraphrased technical recommendations and an unverifiable UTC time window for the second exploit. The founding year (2022) rests solely on RootData and is unverifiable from primary sources. No claims were found to be disputed or contradicted by more credible sources.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}