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 · HECO Bridge & HTX Exchange Hack
- Sequence
- #3
- Score
- 8 → 1 (-7)
- Cluster
- mainnet-beta
- Slot
- 424319672
- Off-chain at
- 2026-06-04T20:53:33.966Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- EstTYvSrqaKYsvxMAvoVWkPf2yngL65DxUdUz3U3cXrP
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1426 chars)
{"actor":"judge","decided_at":"2026-06-04T20:53:33.842Z","decision":"review_revise","investigation_id":"1eeadbe2-acbf-4170-a5c4-155c66503ee2","new_score":1,"page_slug":"heco-bridge-htx","prev_score":8,"reason":"The page's core factual record is well-sourced and largely accurate — 24 of 30 claims confirmed by Tier 1 sources with no outright disputes (disputed_pct 3.3%). However, claim_findings[28] is marked stale: the SEC regulatory section describes litigation against Justin Sun as 'paused for settlement talks' when a full settlement was reached in March 2026 (Rainberry paid $10M, charges against Sun personally dismissed). This is an active factual inaccuracy in a high-priority section, not merely a coverage gap. Additionally, claim_findings[10] identifies an internal inconsistency — the same wallet address (0xe47e6dA16Bb83EB0FD26b3F29b15CE8Fab089B9e) is listed twice as both the 'main exploiter' and a 'separate holding address,' which is misleading in a critical technical section. Two cited URLs supporting the $145M Tornado Cash figure returned 404/403, constituting link rot on notable claims (though the figures are corroborated by other sources). The page should be revised to correct the SEC settlement status and resolve the duplicate wallet address description.","score_delta":-7,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}