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.
- Sequence
- #5
- Score
- 7 → 7 (0)
- Cluster
- mainnet-beta
- Slot
- 457800111
- Off-chain at
- 2026-10-16T22:14:30.082Z
- Anchored at
- 2026-10-16T22:14:45.272Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 7xyUEQkUS8MPNXRWJEK2YSkRHqh8KWCLYePSbau8BNgt
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1912 chars)
{"actor":"reviewer","artifact_identity":"bfb04d24b7de632e543236a09df395ad","decided_at":"2026-10-16T22:14:29.575Z","decision":"review","disputed_pct":0.2308,"findings_hash":"8uJjPyGrh1k3L16N4w59uWVvkGNgVPvd4Zm9VJSrEjLF","investigation_id":"210a0f6a-9ef4-461b-9083-03e89ed7e0c7","mode":"findings_only","new_score":7,"page_content_hash":"16558111ef251a63d44ce21d52b00953757160939412ca8c6f6a9efdf79987db","page_slug":"wanchain-cardano-bridge-night-token-exploit-july-2026","prev_score":7,"reason":"The page's core narrative -- a signature-replay exploit of Wanchain's Cardano-BNB Chain bridge on July 20, 2026, draining ~515.2 million NIGHT via a non-injective TreasuryCheck validator encoding flaw, with Midnight/Cardano unaffected -- is thoroughly and accurately sourced, and the highly specific technical figures (3,110 to 203,001,692 NIGHT, 97.8% reserve depletion, DEX/Liqwid fund disposition, exchange freeze list) check out exactly against the cited technical analysis. Two real defects were found: the van Rossem hard fork date is misstated as July 17, 2026 (actual: July 18, 2026) in three places sharing one root cause, and the claim that 'no compensation plan had been formally announced' is stale, since Wanchain publicly offered a white-hat settlement on July 31, 2026. The ADA 'approached $0.20' claim overstates contemporaneous reporting of ~$0.175-0.178. A handful of Hoskinson quotes/claims in the Midnight Foundation/Cardano Response section are either unverifiable in their exact wording or sourced to material outside the citations actually listed for that section. One archive_url in sources_used points to an unrelated article. The single accepted community submission is broadly consistent with the page but overstates the DEX-liquidation percentage.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}