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 · Silo Finance
- Sequence
- #2
- Score
- 52 → 52 (0)
- Cluster
- mainnet-beta
- Slot
- 425430293
- Off-chain at
- 2026-06-09T23:46:57.653Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- GCxngRLr3jnBy7zpiPREqLu4sZMo3E52sKrdLWxSbZKN
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (995 chars)
{"actor":"reviewer","decided_at":"2026-06-09T23:46:57.577Z","decision":"review","investigation_id":"56838e34-4563-4210-9f8e-bc439f96bf7c","new_score":52,"page_slug":"silo-finance","prev_score":52,"reason":"The investigation page is largely accurate and well-sourced. The core security incidents (IRMv1 vulnerability, RAMSES white-hat drain, audit divergence) are confirmed with high fidelity. The main weaknesses are minor date discrepancies (IRMv2 Arbitrum deployment, Immunefi review publication, 2024 roadmap date), a slight ATH price overstatement ($1.05 vs the $0.91-$0.96 range in primary price trackers), one cryptopanic link returning HTTP 403, and a significant omission: a $545K exploit of a leverage contract on June 25, 2025 is entirely absent from the page, representing a material gap given it is within the investigation's coverage scope.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}