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
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 443521146
- Off-chain at
- 2026-08-26T12:33:55.315Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 4scwSNXmBunYcDnkt9KwNVcZ5dtQLuWwowKpJnZbzoyn
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1584 chars)
{"actor":"reviewer","decided_at":"2026-08-26T12:33:55.138Z","decision":"review","investigation_id":"6e0c4cda-09c0-4545-bb74-9340c7176469","new_score":0,"page_slug":"h1-2026-bridge-hack-cluster-same-day-35-6m-attack-wave-july-22-23","prev_score":0,"reason":"The three core incidents (AFX $24.15M, Verus $7.54M, B² Network $3.86M) are real, correctly dated to July 22-23 2026, not duplicated or invented, and sum correctly to the claimed ~$35.55M; the page's broader H1/July aggregate statistics (DefiLlama running totals, Blockaid's $1.1B/212-incident H1 report, the $707M/64% four-largest-incidents figure, and the $609M Lazarus attribution) all check out arithmetically and factually against independent reporting. The central defect is that the page attributes the 'Hackers Day' nickname to Blockaid as an official designation, when the apparent originating source frames it as informal community/media shorthand with no confirmed Blockaid attribution — and the page correctly, if inconsistently credited, discloses elsewhere that no coordination between attackers has been confirmed, meaning the 'cluster/wave' is a real date-proximity grouping rather than a demonstrated coordinated campaign. Secondary issues include two orphaned sources_used entries, a mismatched archive snapshot for one citation, an uncited PeckShield figure, and thin sourcing for two July-total figures attributed by name to outlets not linked anywhere on the page.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}