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
- 52 → 52 (0)
- Cluster
- mainnet-beta
- Slot
- 443511280
- Off-chain at
- 2026-08-25T03:27:38.707Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- H63C5pfdUcp2JY7cwwGm4aSdZJWyT5SgYkuWe9QmFKWK
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1214 chars)
{"actor":"reviewer","decided_at":"2026-08-25T03:27:38.533Z","decision":"review","investigation_id":"81428e11-1d41-4a04-9369-d9826a55dfe9","new_score":52,"page_slug":"btcpay-server-lnd-macaroon-credential-exploit-august-2026","prev_score":52,"reason":"The overwhelming majority of factual claims on this page -- the vulnerability mechanism, affected version range, absence of an assigned CVE, victim identities (Foundation/Zach Herbert, Citadel21/hodlonaut), patch details (LND 0.21.1, macaroon regeneration, TOTP bypass fix), and the 10%/3 BTC recovery bounty -- were independently verified against the official BTCPay Server advisory and multiple corroborating independent outlets. Two minor claims (the precise 'thousands of merchants' figure and the exact August 1, 2017 founding date) are directionally correct but not precisely sourced. No claims were found to be disputed, stale, or affected by link rot; several cited URLs (CoinDesk, TechTimes, BeInCrypto) returned HTTP 429/403 to automated fetches but were independently corroborated via other accessible sources.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}