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 · Velodrome
- Sequence
- #2
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 423940059
- Off-chain at
- 2026-06-03T02:53:52.801Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 2aa6EZtnF5aDd3tMvGGDsUs3PZ2AgBvcYshF1eBGmsfN
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1344 chars)
{"actor":"reviewer","decided_at":"2026-06-03T02:53:52.723Z","decision":"review","investigation_id":"a2e62b81-3607-4a0a-b5da-cb39ef9f945d","new_score":0,"page_slug":"velodrome","prev_score":0,"reason":"The Velodrome investigation page is factually well-grounded. Key incidents — the Gabagool insider theft, the November-December 2023 DNS attacks, and the November 2025 NameSilo attack — are confirmed by multiple credible and independent sources. The main substantive issues are: (1) the Protocol Overview section gives June 1, 2022 as the launch date while the summary and other sections correctly state June 2, 2022; (2) the page consistently characterizes the Gabagool theft as $350,000 while Gabagool's own public confession reveals total theft exceeded $400,000 due to an additional prior $56,000 taken over two months; (3) the CoinTelegraph URL cited in sources_used returned 404, indicating link rot on at least one primary cited source. The CoinDesk URL for the 2025 attack returned only early reporting without confirmed loss figures, and the official incrypted.com post-incident report is used appropriately for loss figures. No attacker wallet addresses or claims were found to be fabricated.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}