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 · Ledger
- Sequence
- #8
- Score
- 59 → 59 (0)
- Cluster
- mainnet-beta
- Slot
- 464452543
- Off-chain at
- 2026-11-02T09:54:59.358Z
- Anchored at
- 2026-11-02T09:55:29.000Z
- Block time
- 2026-11-02T09:55:29.000Z
Independent verification
- 1. Database (off-chain)
- 2b3b8Eu2BvWRSt5Q6g7xsUgjVKwFGD9ToUSdnMPFvL8s
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1249 chars)
{"actor":"reviewer","artifact_identity":"0c586cefa1be951ed27510f93bca8e7d","decided_at":"2026-11-02T09:54:59.260Z","decision":"review","disputed_pct":0.4286,"findings_hash":"Ektq6hs1fH25QgbaMaGfJDds2Q3hVNAcgo3oQPjaG2uf","investigation_id":"03d5d83f-6247-4200-998e-048db3536286","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":59,"page_content_hash":"1107951b53d99a9e548eb6a22d034e2b3efa2621904fe6741704e05aaf26e92c","page_slug":"ledger","prev_score":59,"reason":"The IPO pause, fake-app theft figures and the Global-e incident are supported. One clear defect: the timeline dates the plaintiff's discovery of the loss to 2026-02, while the page text and press coverage say February 20, 2025. Several details (S-1 status, Apple guideline and account termination, 7M-unit/3% estimate in the cited Protos piece) were not found in the cited sources. Older 2020 and 2023 claims were not verified in this pass.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":8,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}