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 · Lucifer Drainer
- Sequence
- #3
- Score
- 0 → 0 (-7)
- Cluster
- mainnet-beta
- Slot
- 423946111
- Off-chain at
- 2026-06-03T03:33:59.695Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- A2KzH6E72y9nrnRBjgXZnaFsLYSVYBaBw9hhaYZfZQNv
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1759 chars)
{"actor":"judge","decided_at":"2026-06-03T03:33:59.454Z","decision":"review_revise","investigation_id":"1047fc76-44c3-4bf2-a9d6-13e118fe2c6a","new_score":0,"page_slug":"lucifer-drainer","prev_score":0,"reason":"The page has zero disputed claims across 27 checked, and its core operational facts are well-sourced. However, three issues require correction before the page is fully accurate. First, claim_findings[15] shows the $250 million Inferno Drainer theft figure is presented as fact when it is an operator self-report — independently verified estimates at the time of the November 2023 shutdown were $80–87 million, and the page should attribute the $250M claim to the operators. Second, claim_findings[4] and claim_findings[14] both overstate the source: the Bleeping Computer article documents Lucifer Drainer's activity through early 2026 but does not confirm the operation was live at the May 2026 publication date, so the phrasing 'remained live and was actively recruiting' goes beyond what the source establishes. Third, three cited source URLs returned fetch errors (CoinTelegraph 404, BeInCrypto 403, DEXTools connection failure); the CoinTelegraph and BeInCrypto URLs appear in the page's listed sources for sections[4] and sections[6] and should be updated to the corroborating URLs the reviewer identified. The three high-priority coverage gaps — no Lucifer-specific on-chain addresses, no Lucifer-specific victim loss total, and sole-source dependency on the Flare/Bleeping Computer report for all Lucifer-specific claims — are noted for expansion but do not require correction of existing content.","score_delta":-7,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}