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 · Step Finance Hack and Shutdown
- Sequence
- #3
- Score
- 12 → 6 (-6)
- Cluster
- mainnet-beta
- Slot
- 462188792
- Off-chain at
- 2026-10-27T19:27:12.149Z
- Anchored at
- 2026-10-27T19:27:36.000Z
- Block time
- 2026-10-27T19:27:36.000Z
Independent verification
- 1. Database (off-chain)
- AQ3NgBbbWNv2xLY12xxrFnyA3S35nW6nM3mdtRWy9ua9
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1579 chars)
{"actor":"judge","artifact_identity":"d230b9c4c87af2ac2e33a54f077e895b","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T19:27:11.778Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.125,"investigation_id":"417302cd-7090-4909-8dce-29c2cea72ba9","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":6,"page_slug":"step-finance-hack-shutdown-2026","prev_score":12,"reason":"The core facts hold up: the January 31, 2026 breach, the 261,854 SOL loss, the executive-device root cause, the roughly $40M total, the $4.7M recovery, the February 24 shutdown and the token collapse all match tier 1 and tier 2 sources (claim_findings[0-4, 7]). Of the 8 findings that could be checked, 1 (12.5%) could not be verified: the 300,000-350,000 monthly user and 95% protocol coverage figures appear in none of the cited sources (claim_findings[8]). A further finding (claim_findings[5]) was only partly supported: the Kraken delisting dates differ from Kraken's own page on EEA and non-EEA wording. One Tom's Hardware quote could not be checked because the source blocked the reviewer, which is a coverage limit and not a defect of the page. The page correctly states the shutdown, and the only omission is minor, so the penalty stays at the low end of the minor band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-6,"scored_claims":8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}