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 DaaS
- Sequence
- #3
- Score
- 0 → 0 (-12)
- Cluster
- mainnet-beta
- Slot
- 443519843
- Off-chain at
- 2026-08-26T09:04:26.060Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- Bzg96hm5Pw2UfYCXoynGi65PpqCSLVc3EmTH63FRHCpv
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2284 chars)
{"actor":"judge","decided_at":"2026-08-26T09:04:25.853Z","decision":"review_revise","investigation_id":"290c0f45-6d7c-4e0d-9ead-b049aaa7e965","new_score":0,"page_slug":"lucifer-daas","prev_score":0,"reason":"Of 22 checked claims, 3 were disputed and 0 were unverifiable, giving a disputed rate of 13.6% (3/22), which falls in the minor-issues band. The page's core account of Lucifer DaaS itself — its existence, affiliate commission structure, version history, platform-ban resilience, and the absence of operator attribution or enforcement action — is well supported by the cited BleepingComputer/Flare reporting and holds up (claim_findings[0], [1], [4]-[12], [19], [21]). The disputed items are two duplicated instances of the same defect, where the page lists specific rival drainer brands (Vanilla, Quark, Pink, MS Drainer, CLINKSINK) that do not appear in the sources cited for those passages — the cited article names a different competitor set entirely (claim_findings[3], [13]). A third disputed item attributes a 2023 shutdown quote and rationale ('too much attention') to Inferno Drainer that does not match the cited source, which instead calls the shutdown a 'diversionary tactic,' with independent reporting showing different actual wording (claim_findings[20]). None of these three touch the central allegations against Lucifer DaaS; they involve peripheral comparisons to other criminal operations, so the harm is a sourcing-precision failure rather than a factual collapse of the page's core thesis. Two additional claims were only partially supported: an unattributed 'ransomware-as-a-service' analogy and 'significant maturation' framing, and an unattributed 'first'/'most specific published research' claim (claim_findings[2], [18]) — both are the page's own editorializing beyond what sources state, but these are excluded from the disputed-percentage calculation and are lower-severity than fabricated facts. Coverage gaps were all medium or low priority, including that the page omits reader-facing defensive guidance present in its primary source, and none rise to a level that would independently force escalation.","score_delta":-12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}