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.
- Sequence
- #2
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 443506007
- Off-chain at
- 2026-08-08T04:39:02.623Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 6Dj3nd1Gafc4iE567WTsUykmCePtFXyiUyh2KtLAhaYp
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1251 chars)
{"actor":"reviewer","decided_at":"2026-08-08T04:39:02.548Z","decision":"review","investigation_id":"3e006894-1e8f-4d75-9ffa-6a43c96da138","new_score":0,"page_slug":"h2-2026-july-bridge-hack-wave-seven-attacks-m-lost","prev_score":0,"reason":"The page is well-sourced and factually accurate on the specific incident details for all seven attacks: amounts, dates, attack vectors, and technical mechanics are confirmed by independent sources including Tier-1 outlets (CoinDesk, The Block, CoinTelegraph) and security firm post-mortems (Halborn, BlockSec). The primary reliability concerns are: (1) the '$328.6M year-to-date through July' framing is temporally misleading — this figure dates from mid-May 2026, and the July source cited explicitly calls it an 'earlier in the year' running tab; (2) the Systemic Analysis section contains an internal counting error, labeling nine attacks as 'seven core incidents'; (3) the Coldcard loss estimate of $110M falls below TRM Labs' authoritative $116M figure; and (4) a material partial recovery (Across exploiter returning $623.9K on July 28) is absent from the page.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}