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 Bridge
- Sequence
- #4
- Score
- 56 → 56 (0)
- Cluster
- mainnet-beta
- Slot
- 464299011
- Off-chain at
- 2026-11-02T00:47:26.557Z
- Anchored at
- 2026-11-02T00:47:29.000Z
- Block time
- 2026-11-02T00:47:29.000Z
Independent verification
- 1. Database (off-chain)
- Gisz7pHbaXXdWAvChaa5ascPoZqiYLELhBt2R84zkT3f
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1335 chars)
{"actor":"judge","artifact_identity":"d4c0b61b898a735672ac7238e66bcbd3","band_override":null,"decided_at":"2026-11-02T00:47:26.322Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.5,"investigation_id":"79936410-60d3-4110-99c0-307d46ae1983","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":56,"page_slug":"harmony-bridge","prev_score":56,"reason":"Of 10 checked claims, 2 were disputed and 3 could not be found in any fetched source, giving 50% disputed or unverifiable, which falls in the significant-issues band. The 99.9% Railgun concentration figure (claim_findings[0] and [1]) contradicts the cited Elliptic article, which says about 70%. The 124 BTC exchange freeze and the 25,500 ETH routing including OKX (claim_findings[2], [3], [4]) were not found in the cited sources. The core account holds up: the June 2022 exploit, the 2-of-5 multisig, the FBI attribution to Lazarus on 2023-01-23, the $60M Railgun deposit and the March 2025 Tornado Cash delisting were all corroborated, so the penalty sits at the lighter end of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}