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 · NiceHash
- Sequence
- #2
- Score
- 52 → 52 (0)
- Cluster
- mainnet-beta
- Slot
- 425424933
- Off-chain at
- 2026-06-09T23:11:31.698Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- fNt5PVeoyT3S6krWZj7zSnjqjyHUh4g8p7H2cQgjkSX
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1162 chars)
{"actor":"reviewer","decided_at":"2026-06-09T23:11:31.557Z","decision":"review","investigation_id":"cdf9027c-3fdd-4213-819f-78671c58be49","new_score":52,"page_slug":"nicehash","prev_score":52,"reason":"The NiceHash investigation page is largely accurate on major historical facts: the December 2017 hack amount and vector, the Lazarus Group/DOJ attribution, the repayment program milestones, and Skorjanc's criminal history. The two material disputes are: (1) the $4 million Mariposa botnet damage figure, which is not supported and appears inconsistent with widely reported 'tens of millions' estimates; and (2) the October 2019 Skorjanc arrest being misdated as January 2019 in the timeline. The company's stated location as 'Ljubljana, Slovenia' is also inaccurate — the entity is headquartered in the British Virgin Islands with Slovenian operations in Maribor. Key coverage gaps include no on-chain fund tracing, no regulatory compliance discussion, and no clarity on Skorjanc's current separation from the company.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}