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 · NiceHash
- Sequence
- #3
- Score
- 52 → 42 (-10)
- Cluster
- mainnet-beta
- Slot
- 425424936
- Off-chain at
- 2026-06-09T23:11:31.807Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 2NXjsacrq9xZ7pf6BfuGuA5CrR3pxaeyi9xjLh3k6sZX
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1521 chars)
{"actor":"judge","decided_at":"2026-06-09T23:11:31.557Z","decision":"review_revise","investigation_id":"cdf9027c-3fdd-4213-819f-78671c58be49","new_score":42,"page_slug":"nicehash","prev_score":52,"reason":"The reviewer found 2 disputed and 4 partially-supported claims out of 24 total, yielding a disputed_pct of 12.5% — in the minor-issues band. The core historical record (hack vector and date, BTC quantity stolen, Lazarus Group attribution, DOJ indictment details, and the full repayment program timeline) is well-supported. The two disputed findings are: claim_findings[18], the '$4 million Mariposa botnet damages' figure, which is contradicted by three sources including a Tier 1 Krebs report that describes damages as far higher; and claim_findings[22], the timeline entry dating Skorjanc's arrest as 2019-01-01, which multiple Tier 1 sources place in October 2019. Additionally, claim_findings[7] incorrectly states operations were suspended for approximately 24 hours when Wikipedia confirms the platform was down until December 21 — roughly 15 days — a meaningful error in a critical-severity section. The page also misidentifies the company's primary Slovenian location as Ljubljana when sources indicate Maribor. No link rot or stale citations were found. One high-priority coverage gap (on-chain fund tracing) was identified but does not by itself warrant denial.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}