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 · Triple-A
- Sequence
- #4
- Score
- 74 → 74 (0)
- Cluster
- mainnet-beta
- Slot
- 464283240
- Off-chain at
- 2026-11-01T23:50:47.254Z
- Anchored at
- 2026-11-01T23:51:11.000Z
- Block time
- 2026-11-01T23:51:11.000Z
Independent verification
- 1. Database (off-chain)
- 2VHwAj35K3U4y7s6yeFmQtgZwcwWScfQkC9qwBsqG8GD
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1382 chars)
{"actor":"reviewer","artifact_identity":"a93a40da184b7ea64c3fb7d9619ab8ab","blocked_count":2,"decided_at":"2026-11-01T23:50:47.189Z","decision":"review","disputed_pct":0,"findings_hash":"HVoAqyBEW72McYHWMpwoDzrjfEi7SQe8877kYNAfaXUB","investigation_id":"65207d30-5c8e-4200-9ae0-987fe4256102","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":74,"omissions":{"material":0,"total":1},"page_content_hash":"2546b54a7dfdbb6fc4e9f746d74cb104e1182f142d2f49c2b08850931d2bd6de","page_slug":"triple-a","prev_score":74,"reason":"The incident section is well supported by Tier-1 and Tier-2 reporting (Cointelegraph, Coin Republic): the July 27 confirmation, the client funds statement, the maintenance window, the SPF involvement, the Specter estimate and the lack of disclosed cause all match. One internal tension: access is dated July 25 while outflows are said to have been flagged July 24. Licensing, funding, partnership and review-site claims were not checked in this limited pass. No current-status contradictions were found.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":3,"sequence_num":4,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}