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 · numa.
- Sequence
- #3
- Score
- 45 → 45 (0)
- Cluster
- mainnet-beta
- Slot
- 464370490
- Off-chain at
- 2026-11-02T05:02:27.554Z
- Anchored at
- 2026-11-02T05:02:49.000Z
- Block time
- 2026-11-02T05:02:49.000Z
Independent verification
- 1. Database (off-chain)
- 2dNjRmS3i5Rci2VAd8ue28pjaMA7CvM3PAMSg1JAQAQV
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1362 chars)
{"actor":"reviewer","artifact_identity":"0b16c62a70dac492049d04b84046870e","decided_at":"2026-11-02T05:02:27.510Z","decision":"review","disputed_pct":0.4286,"findings_hash":"5JAYh3CWsoSJs5g5dUN2p29EVXCT9Mx77EcmQJDWMuAD","investigation_id":"4e0807c8-b31e-45cb-8db3-3c303761446e","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":45,"omissions":{"material":0,"total":1},"page_content_hash":"ac937b7aa331b0ca0cf0c8ad133a6c23174e0cd0a757d2dc131f44168aacdd05","page_slug":"numa","prev_score":45,"reason":"The core incident facts, covering both exploits' dates, amounts, mechanisms, addresses and Tornado Cash laundering, match the vendor and primary sources I fetched. Problems found: the compensation-plan timeline date (the plan is bylined Apr 28, not Apr 21), the unsourced ZachXBT claim in the summary, an unverified audit-recommendation claim attributed to CertiK and Verichains, and a paraphrase of the team's compensation statement that I could not find in the source. Current operating status could not be determined.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}