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 · Cronos Chain
- Sequence
- #2
- Score
- 32 → 32 (0)
- Cluster
- mainnet-beta
- Slot
- 443561972
- Off-chain at
- 2026-09-02T00:40:52.924Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- GseMYnF91zPesq7VFhHTZ9PiJGrWNhDbzDqGeWFHZAn7
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1230 chars)
{"actor":"reviewer","artifact_identity":"5fc250da61a2f9549f8e74273cd28267","decided_at":"2026-09-02T00:40:52.825Z","decision":"review","disputed_pct":0.1538,"investigation_id":"e3823bba-5389-460a-8e33-c4d19489b6bd","new_score":32,"page_slug":"cronos-chain","prev_score":32,"reason":"The large majority of the page's factual claims about the Tectonic exploit, the Cronos chain halt and rollback, and the 2025 CRO reissuance controversy are independently corroborated by tier-1 and tier-2 sources, including primary documentation from Tectonic and Cronos themselves. The most notable defect is a timeline error: the page dates the 2021 CRO token burn to November 1, 2021 (identical to the Cronos EVM mainnet launch date used elsewhere on the page), while independent reporting places the burn in February 2021 — the two distinct 2021 events appear to have been conflated. A handful of granular figures (TONIC's $929M/57-month cumulative volume, specific bad-debt and liquidation totals, the 'one in eight hacks' ratio) could not be independently corroborated but were also not contradicted.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}