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 · Hacken Token
- Sequence
- #2
- Score
- 42 → 42 (0)
- Cluster
- mainnet-beta
- Slot
- 443508383
- Off-chain at
- 2026-08-18T17:40:30.866Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 5sYhrYCZ2YZgS2oeVVtdCwf1W31Y9e1xXPFCBamMfpEG
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1363 chars)
{"actor":"reviewer","decided_at":"2026-08-18T17:40:30.758Z","decision":"review","investigation_id":"8be993d6-1435-4c2e-9d86-fe00f9f22a62","new_score":42,"page_slug":"hacken-token","prev_score":42,"reason":"The page's central narrative — a private key compromised during a bridge migration, ~900M HAI minted and ~$250K dumped, a near-99% price collapse, and a CEO admission of a five-year multisig deferral — is well corroborated by multiple independent tier-1/tier-2 outlets and Hacken's own public statements. Two defects were found: the ATH timeline entry conflates the true all-time-high price (reached April 2021) with a much lower March 2024 secondary peak, and the ZachXBT/AVOID.NET risk-classification claim is uncited and unverifiable. The most significant issue is structural, not factual: every section in this snapshot has empty heading/content fields, leaving only source-list clusters with no prose for a reader or reviewer to check claims against — this is a data/rendering defect that should be corrected independent of the score question. No unhedged criminal allegations were found; the page consistently and correctly frames Hacken as the victim of a security failure rather than a perpetrator of fraud.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}