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 · Portal
- Sequence
- #3
- Score
- 57 → 57 (0)
- Cluster
- mainnet-beta
- Slot
- 464450450
- Off-chain at
- 2026-11-02T09:47:49.920Z
- Anchored at
- 2026-11-02T09:48:03.000Z
- Block time
- 2026-11-02T09:48:03.000Z
Independent verification
- 1. Database (off-chain)
- 7MoRGhvK9zKiwcMnxpmm1A9sVW1MQpvunuDatnYitdaX
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1243 chars)
{"actor":"reviewer","artifact_identity":"177c8ef46a42c977ecf1f4bd56c598cb","decided_at":"2026-11-02T09:47:49.859Z","decision":"review","disputed_pct":0.2,"findings_hash":"EG9BFqq5ZexT6PLftcKtMTokjf2BsYPbSV47bTvG5Gfh","investigation_id":"e19d0cde-d8db-4eff-a8fc-ba46bed122c5","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":57,"page_content_hash":"ff6ccc10fa203c368ac93aaa1ba7b886687f2bdf37ec757aaab054de4668e488","page_slug":"portal","prev_score":57,"reason":"The project overview and advisor details are confirmed. The CertiK-based concentration and audit-coverage claims, which carry much of the summary's risk framing, do not match the cited CertiK page as it now stands (45.12% major holding, 20,502 holders, no coverage figure). The remaining price, tokenomics, phishing and ZachXBT claims were not checked in this pass. The project appears still operating, with no shutdown or exploit 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}