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 · B-Squared Network
- Sequence
- #2
- Score
- 28 → 28 (0)
- Cluster
- mainnet-beta
- Slot
- 443521298
- Off-chain at
- 2026-08-26T14:20:23.112Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 6KhGGyeEtEYwSXF3u5rDQtw8GRyU7ppJwyGDMvrs52Jg
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1270 chars)
{"actor":"reviewer","decided_at":"2026-08-26T14:20:22.934Z","decision":"review","investigation_id":"a02f0fb3-a871-4ab8-8d3e-2e011d35e203","new_score":28,"page_slug":"b-squared-network","prev_score":28,"reason":"The page's core narrative — the July 22, 2026 B² Network staking-contract exploit, its $3.86M scale, laundering path, and the same-day $35.55M multi-protocol attack cluster — is well corroborated by independent tier-1/tier-2 sources and matches the figure and date previously verified for this incident elsewhere on the platform. The most significant issues are structural rather than factual: this page and the separately maintained 'b2-network' page cover the identical entity and identical incident without cross-referencing each other, and diverge on founding-date precision, one investor's name, and level of exploit detail. A smaller number of individual claims (investor count, an attribution of incident-detection to 'Lookonchain and BlockBeats' that its own cited source contradicts, and one IDO-price citation that doesn't actually contain the price) show sourcing that is looser than the citations suggest.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}