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 · Harmony ONE (Protocol Entity)
- Sequence
- #3
- Score
- 14 → 8 (-6)
- Cluster
- mainnet-beta
- Slot
- 443510370
- Off-chain at
- 2026-08-25T02:47:24.330Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- EW8TbK8L2dvXKhaEQFhvNXhB4fedcmYg7MPHk17puo5j
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1695 chars)
{"actor":"judge","decided_at":"2026-08-25T02:47:23.748Z","decision":"review_revise","investigation_id":"92b40233-bfe5-4980-b742-f3d9e6b014e2","new_score":8,"page_slug":"harmony-one-protocol-entity","prev_score":14,"reason":"None of the page's core allegations were found false: the 2022 Horizon Bridge hack, its FBI/Lazarus Group attribution, and the August 2026 cross-shard mint exploit and rollback are all independently corroborated by multiple Tier 1-2 sources with zero disputed claims. However, recomputed over the reviewer's full 30-item claim_findings array, 3 of 30 claims (10.0%) land as unverifiable, and several other items show real friction: the single most heavily relied-upon source for granular 2026 incident details (an official X/Twitter post) returned HTTP 402 with no archived snapshot, leaving the precise attack-start block number unconfirmed (claim_findings[15]) and the emergency-patch halt block only partially supported (claim_findings[19]). The claim that both shards were 'stable' and had advanced from epoch 3002 to 3004 as of August 21 rests solely on a dynamically-updating AI aggregator page rather than a fixed, citable source (claim_findings[24]). Separately, the page's blanket statement that stolen Horizon Bridge funds were 'not recovered' omits contemporaneous reporting of a partial ~124 BTC interception (claim_findings[12]). These are citation-durability and completeness issues rather than factual disputes, so a modest downward adjustment with no status change is warranted rather than a more severe penalty.","score_delta":-6,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}