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 · Onyx V2
- Sequence
- #3
- Score
- 52 → 52 (0)
- Cluster
- mainnet-beta
- Slot
- 464366307
- Off-chain at
- 2026-11-02T04:47:23.289Z
- Anchored at
- 2026-11-02T04:47:50.000Z
- Block time
- 2026-11-02T04:47:50.000Z
Independent verification
- 1. Database (off-chain)
- BcYoMrfkevwLW9oNdANryJsLCNJCr2mmqQ76P2tWTHdd
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1602 chars)
{"actor":"reviewer","artifact_identity":"9bfc1e5b4ec7c58ad8aafe2bcccb9c67","decided_at":"2026-11-02T04:47:23.231Z","decision":"review","disputed_pct":0.5,"findings_hash":"Ab8w9GVdCdpnt7ZvRRZ6fPaXwGkXYDR6DMdyhzfDhpPx","investigation_id":"8748bbad-08ea-40ed-9e62-add2d3a037e6","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":52,"omissions":{"material":0,"total":1},"page_content_hash":"69a3f335d75f9917b349dcc2ac54336133ac000072d46bae9b021a7c474f654d","page_slug":"onyx-v2","prev_score":52,"reason":"The core exploit narrative holds: the second-exploit figures, attacker address, transaction hash and flash-loan details match rekt, and the first-exploit amounts, address, Tornado Cash split and Proposal 22 vote concentration match rekt. The main defect is that the first exploit is dated 2 Nov 2023, which is rekt's publication date. The exploit happened on Tuesday 31 Oct 2023. Two quoted passages (rekt on community vigilance and Halborn on the same vulnerability) were not found verbatim. The 87% TVL drop and the 100% OIP-46 approval were not located in the sources read. The V2 launch date is inconsistent across the summary, timeline and section. The XCN price is dated May 2026 and is likely stale. No current shutdown, exploit or sanction was found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}