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
- Sequence
- #2
- Score
- 28 → 28 (0)
- Cluster
- mainnet-beta
- Slot
- 443562467
- Off-chain at
- 2026-09-02T00:43:07.882Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 8T3FwDkZ2rJNrnjyyX1soEpZNVBDL2k552qGLNrrqDve
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1403 chars)
{"actor":"reviewer","artifact_identity":"24a3aeaf096ec84b9a55402e0faa72d3","decided_at":"2026-09-02T00:43:07.729Z","decision":"review","disputed_pct":0.2105,"investigation_id":"a56e663a-d007-4dbb-ba10-07e27f706ebd","new_score":28,"page_slug":"harmony-one-august-2026-layer-1-mint-exploit","prev_score":28,"reason":"The page's core narrative (unauthorized minting of ~4 billion ONE via a consensus quorum-verification flaw, ~97% reaching exchanges, emergency patch, and full blockchain rollback) is well corroborated across multiple independent tier-1 and tier-2 outlets and matches the primary sources cited. The most significant issue found is an unreconciled internal inconsistency between the page's repeated '~4 billion tokens minted' headline figure and its own citation of a wallet that allegedly moved 2.385 trillion forged ONE, a discrepancy that traces back to inconsistent reporting across the underlying sources themselves (also seen in Forklog and Lookonchain reporting ~3.01 trillion from 'later analysis'). The claim of two chained vulnerabilities is only fully corroborated by one of four cited sources. Minor numeric friction also exists in the DEX-share-of-rollback-transactions figure (96% vs. an implied ~91.5% from raw counts in one source).","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}