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 · numa.
- Sequence
- #4
- Score
- 45 → 45 (0)
- Cluster
- mainnet-beta
- Slot
- 464370495
- Off-chain at
- 2026-11-02T05:02:27.715Z
- Anchored at
- 2026-11-02T05:02:50.000Z
- Block time
- 2026-11-02T05:02:50.000Z
Independent verification
- 1. Database (off-chain)
- 41NdSkEczSyLqmKrxENUXV9K5CEia3dnziTxxVKeEebq
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1416 chars)
{"actor":"judge","artifact_identity":"0b16c62a70dac492049d04b84046870e","band_override":null,"decided_at":"2026-11-02T05:02:27.510Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4286,"investigation_id":"4e0807c8-b31e-45cb-8db3-3c303761446e","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":45,"page_slug":"numa","prev_score":45,"reason":"Three of seven reviewed claims (about 43%) were disputed or could not be verified. The compensation plan is dated 2025-04-21 but the source is bylined 2025-04-28 (claim_findings[1]). The summary says ZachXBT flagged the entity, but no source supports this (claim_findings[0]). The statement that CertiK and Verichains both concluded an audit with stress-testing was essential was not found in the CertiK analysis, and the Verichains page was not checked (claim_findings[6]). The core facts of both exploits, covering dates, amounts, addresses and Tornado Cash laundering, were confirmed (claim_findings[3], [4]). The penalty is kept at the low end of the band because the reviewer's confidence is only moderate and the problems sit in secondary claims, not the core allegations.","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}