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_revise · Boltz Bitcoin Bridge
- Sequence
- #3
- Score
- 42 → 34 (-8)
- Cluster
- mainnet-beta
- Slot
- 443510757
- Off-chain at
- 2026-08-25T03:08:21.856Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- JixF4Z48vutA86uyB8P6jYs8P95fSVpFGQv1kC53Rq9
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1522 chars)
{"actor":"judge","decided_at":"2026-08-25T03:08:21.606Z","decision":"review_revise","investigation_id":"2b664b6f-b5d4-4fb4-9681-789b29bd7e8d","new_score":34,"page_slug":"boltz-bitcoin-bridge","prev_score":42,"reason":"The fact-check found no disputed claims among 41 items checked (disputed_pct 4.9%), and the central narrative -- the August 3 suspension, its stated AI-related cause, the ~$262,000 TVL figure, the warrant canary timeline, and the founder exit -- is corroborated verbatim by multiple independent outlets (claim_findings[1], [15]-[17], [25]-[29]). That said, the page states on its own authority that Boltz is the 'first publicly documented' case of a service self-shutting down over AI-accelerated exploitation, a superlative no cited source actually makes (claim_findings[37]). The review also flagged a high-priority coverage gap: no source provides technical detail (attack vectors, what was actually compromised) behind the central 'several exploits succeeded' claim. Combined with a handful of minor precision issues -- an imprecise incorporation date, an uncited editorial 'single point of failure' framing, an unsourced 'gratitude' characterization, and a status-date/citation mismatch (claim_findings[7], [4], [22], [23]) -- these push the page toward a light revision rather than a clean approval, though nothing found undermines the page's core claims.","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}