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
- Sequence
- #10
- Score
- 49 → 49 (0)
- Cluster
- mainnet-beta
- Slot
- 464589061
- Off-chain at
- 2026-11-02T18:03:32.953Z
- Anchored at
- 2026-11-02T18:03:39.000Z
- Block time
- 2026-11-02T18:03:39.000Z
Independent verification
- 1. Database (off-chain)
- 9ca61gJuU8aHMA31vvAYBNLDQv5AN7SaXFwAco27H4vk
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1787 chars)
{"actor":"judge","artifact_identity":"7165bb8001588d664428ea5457672629","band_override":null,"decided_at":"2026-11-02T18:03:32.624Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1667,"investigation_id":"6670b7ec-4df8-4b8c-8b6d-d167cc148fd6","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":49,"page_slug":"step-finance","prev_score":49,"reason":"Of 12 reviewed claims, 2 could not be verified (claim_findings[5] on Remora being isolated from the incident, and claim_findings[8] on the all-time-high price figures), giving a disputed share of about 17%. The central account holds up: the breach, the roughly $40M loss estimate, the recovery of about $4.7M and the February 23 shutdown are confirmed by multiple outlets. Problems are the unsupported 'led by' wording for the 2021 funding round (claim_findings[9] and [10]), the single lower-tier source for the July laundering (claim_findings[3]), and a material omission: SolanaFloor was later acquired by the Jito Foundation and resumed operations, which the page does not mention.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":10,"severity_override":{"applied":true,"band":"minor","from_band":"minor","reason":"The review reports a material omission: SolanaFloor was acquired by the Jito Foundation and resumed operations on 2026-03-10, so the page's statement that it stopped publishing is out of date. The page's core account of the breach and shutdown is accurate and the subject status does not contradict it, so the verdict is held at the minor band rather than raised further."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}