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
- Sequence
- #2
- Score
- 38 → 38 (0)
- Cluster
- mainnet-beta
- Slot
- 443505300
- Off-chain at
- 2026-08-08T01:44:21.841Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 9i7GyriCxT67EuNHDTTNQaKchuduXNiViqsbq8NHi5aN
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1004 chars)
{"actor":"reviewer","decided_at":"2026-08-08T01:44:21.765Z","decision":"review","investigation_id":"12a321b4-9440-4a20-ba03-e25b6c779bc2","new_score":38,"page_slug":"across-protocol-solana-bridge-exploit-july-2026","prev_score":38,"reason":"The investigation is strongly sourced and factually accurate for the core incident: attack mechanics, timeline, loss figures, attacker fund routing, protocol response, governance context, and broader July 2026 bridge hack landscape are all confirmed by independent, credible sources. The main deficiencies are one dead and misattributed URL in the sources_used list (the CoinDesk STRIDE article is referenced with an incorrect, 404 URL), one unverifiable Solana attacker address, and one unconfirmed claim that Across specifically participated in the STRIDE program. No claims were found to contradict credible reporting.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}