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 · Starknet
- Sequence
- #3
- Score
- 60 → 45 (-15)
- Cluster
- mainnet-beta
- Slot
- 425200058
- Off-chain at
- 2026-06-08T22:21:00.931Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 9kiZnXGxAd7URYb6gRbnJNjNRUA3MPd9GCtVAAN1zrkb
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1468 chars)
{"actor":"judge","decided_at":"2026-06-08T22:21:00.752Z","decision":"review_revise","investigation_id":"60467ada-cfc0-4f9d-9b8c-1b4c334089c8","new_score":45,"page_slug":"starknet","prev_score":60,"reason":"The reviewer identified 3 disputed claims out of 28 checked (10.7%), placing this in the minor-issues band. However, the disputes include one substantive factual error: claim_findings[23] states the zkLend attacker returned approximately $3.2 million, which is contradicted by multiple sources showing the attacker lost most funds to a Tornado Cash phishing scam and zkLend wound down with only $200K for user recovery. This error appears in a high-severity section and is directly misleading to readers assessing ecosystem risk. Additionally, claim_findings[6] incorrectly states the alpha mainnet launched November 16, 2021 in the section text (the correct date is October 4, 2021), and claim_findings[14] cites the original unlock quantum as 13.1% when Tier 1 sources report 13.4%. Two high-priority coverage gaps further support revision: the zkLend recovery correction and the stale 'late 2025 leading ZK-rollup by TVL' claim, which 2026 data shows was overtaken by ZKsync Era. The score delta is set at the upper end of the minor-issues band given the zkLend error's misleading nature in a high-severity section.","score_delta":-15,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}