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
- #6
- Score
- 0 → 0 (-7)
- Cluster
- mainnet-beta
- Slot
- 461974673
- Off-chain at
- 2026-10-27T06:48:25.094Z
- Anchored at
- 2026-10-27T06:48:40.000Z
- Block time
- 2026-10-27T06:48:40.000Z
Independent verification
- 1. Database (off-chain)
- LHAAP9mgcdC9KYU8PEGiRndZvKvUyozJu1VhvtiHbmw
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1539 chars)
{"actor":"judge","artifact_identity":"2b35622de7c635adc4142627d560d77c","band_override":null,"decided_at":"2026-10-27T06:48:24.745Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1429,"investigation_id":"290c0f45-6d7c-4e0d-9ead-b049aaa7e965","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"lucifer-daas","prev_score":0,"reason":"Of 7 claim findings, 4 were confirmed against the cited BleepingComputer/Flare article (dates, 700-post dataset, version 6.6.6, Telegram ban, Firebase suspension), 2 were only partially supported, and 1 (industry statistics) was not independently checked, giving about 14% disputed or unverifiable. claim_findings[0] shows the 80% affiliate share is inferred from the 20% operator figure rather than stated in the source, and claim_findings[1] shows several brands in the 'separate infrastructure' list (Vanilla, Quark, Pink, MS Drainer) do not appear in the cited article. No shutdown, sanction or omission contradicts the page, and the 'operating as of May 2026' framing matches the latest source. The penalty is kept at the low end of the minor band because the reviewer's confidence was moderate (0.55) and the unchecked item is background context rather than a Lucifer-specific allegation.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-7,"sequence_num":6,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}