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 · Step Finance Hack and Shutdown
- Sequence
- #2
- Score
- 12 → 12 (0)
- Cluster
- mainnet-beta
- Slot
- 462188787
- Off-chain at
- 2026-10-27T19:27:11.953Z
- Anchored at
- 2026-10-27T19:27:35.000Z
- Block time
- 2026-10-27T19:27:35.000Z
Independent verification
- 1. Database (off-chain)
- FGuEP2m7rsyw32YTroTmekyniEk91rd4vHpmJTba58CZ
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1427 chars)
{"actor":"reviewer","artifact_identity":"d230b9c4c87af2ac2e33a54f077e895b","blocked_count":1,"decided_at":"2026-10-27T19:27:11.778Z","decision":"review","disputed_pct":0.125,"findings_hash":"31XDTFpB29rWdf9GMhU4uN9KyUE9cGK7XX47avWr57we","investigation_id":"417302cd-7090-4909-8dce-29c2cea72ba9","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":12,"omissions":{"material":0,"total":1},"page_content_hash":"f6dd579e564d0b04a41fcbb3f155bddff25c3dd5157347b8045a02ed94af7b2f","page_slug":"step-finance-hack-shutdown-2026","prev_score":12,"reason":"The core facts hold: the Jan 31, 2026 breach, the 261,854 SOL loss, the executive-device root cause, the roughly $40M total, the $4.7M recovery, the Feb 24 shutdown and the token collapse all match the tier-1 and tier-2 sources I fetched. Issues are the Kraken delisting dates (the page and Kraken's page differ on EEA and non-EEA wording), a Tom's Hardware quote I could not check, and the 300,000-350,000 MAU and 95% coverage figures, which I could not find in the cited sources. The page states the shutdown correctly.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":8,"sequence_num":2,"subject_status":"shut_down","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}