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 · Cronos Chain
- Sequence
- #3
- Score
- 32 → 26 (-6)
- Cluster
- mainnet-beta
- Slot
- 443561975
- Off-chain at
- 2026-09-02T00:40:53.021Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- AnFPb4BEza9qiDcDu8kvnxyJCJ8znuGSJxGtYKv3Nsc3
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1713 chars)
{"actor":"judge","artifact_identity":"5fc250da61a2f9549f8e74273cd28267","band_override":null,"decided_at":"2026-09-02T00:40:52.825Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1538,"investigation_id":"e3823bba-5389-460a-8e33-c4d19489b6bd","new_score":26,"page_slug":"cronos-chain","prev_score":32,"reason":"The review corroborated the large majority of the page's claims (18 of ~24 fully confirmed, disputed_pct 13%), including the central facts of the $75M Tectonic exploit, the chain-wide halt and rollback, and Crypto.com's organizational ties to Cronos Labs and Tectonic. The one disputed finding is a timeline date error: the page dates the 2021 CRO token burn to November 1, 2021 (the same date used for the unrelated Cronos EVM mainnet launch), while independent sourcing places the burn in February 2021 (claim_findings[23]). Two additional claims were only partially supported on precision grounds — the mainnet launch date is off by about a week (claim_findings[22]) and the '87% community opposition' figure is the high end of a reported range rather than a settled number (claim_findings[7]) — and several granular figures (TONIC's cumulative trading volume, bad-debt and liquidation totals, a derivative 'one in eight hacks' ratio) could not be independently verified but were also not contradicted (claim_findings[10], [20], [21]). No link rot or stale-source findings were reported, and the reviewer's confidence (0.78) supports treating these as correctable precision issues rather than a breakdown of the page's core narrative.","score_delta":-6,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}