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 · Onyx V2
- Sequence
- #4
- Score
- 52 → 52 (0)
- Cluster
- mainnet-beta
- Slot
- 464366312
- Off-chain at
- 2026-11-02T04:47:23.479Z
- Anchored at
- 2026-11-02T04:47:51.000Z
- Block time
- 2026-11-02T04:47:51.000Z
Independent verification
- 1. Database (off-chain)
- FV7XnjTXAh3euiUZvUFS5higBE2SUMBfnBkECXR4jSgo
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1469 chars)
{"actor":"judge","artifact_identity":"9bfc1e5b4ec7c58ad8aafe2bcccb9c67","band_override":null,"decided_at":"2026-11-02T04:47:23.231Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.5,"investigation_id":"8748bbad-08ea-40ed-9e62-add2d3a037e6","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":52,"page_slug":"onyx-v2","prev_score":52,"reason":"Of 12 reviewed claims, 2 were disputed and 4 could not be verified, giving a disputed rate of 50%. The first exploit is dated 2 November 2023 in both the timeline and the narrative (claim_findings[0], [1]), but that is the publication date of the source article. The exploit happened on 31 October 2023. The 87% TVL drop, the 100% OIP-46 approval, a rekt.news quote and the CertiK audit claims were not found in the sources checked (claim_findings[2], [6], [10]), and the V2 launch date is inconsistent across the page (claim_findings[8]). The core exploit facts for both hacks (amounts, addresses, transaction hash, Tornado Cash split) match the sources, and no shutdown or sanction was found, so the penalty sits at the lower end of the band. The reviewer's confidence was moderate (0.55) and many cited sources were not fetched.","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}