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 · NEAR Protocol
- Sequence
- #5
- Score
- 64 → 64 (0)
- Cluster
- mainnet-beta
- Slot
- 462905052
- Off-chain at
- 2026-10-29T13:53:41.336Z
- Anchored at
- 2026-10-29T13:53:59.000Z
- Block time
- 2026-10-29T13:53:59.000Z
Independent verification
- 1. Database (off-chain)
- 4Pmdn12C31TL91TkfbXMnKCQNtdZKyGW9VbHcSG8xtfW
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1382 chars)
{"actor":"reviewer","artifact_identity":"c1dfd4de3a85e4ab4c3572a0ea0bcd7e","blocked_count":1,"decided_at":"2026-10-29T13:53:41.147Z","decision":"review","disputed_pct":0.1429,"findings_hash":"4pGbbAgbSkYwkwSYUsSEQk4sLx2wgRrs6k2LQiWn8QG7","investigation_id":"5dfc3991-d810-433a-868c-cc8880f85b96","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":64,"omissions":{"material":1,"total":1},"page_content_hash":"c3c836c935d4029077cd6036e1e9998b3e8473abedad13f8514f183b31072781","page_slug":"near-protocol","prev_score":64,"reason":"The core facts checked hold: the Oct 1, 2026 NEAR Intents breach, the SEC/Coinbase dismissal date, NEAR's inclusion in the 2023 complaint, and the Nightshade 2.0 date. Weaknesses are citation mismatches (the Bitwise ETF launch is cited to a 2025 filing story, and the Cointelegraph dismissal piece does not mention NEAR or fines). One material omission: the NEAR Intents funds were returned in full on Oct 3. Many governance, funding and Wikipedia-sourced claims were not verified in this pass.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":7,"sequence_num":5,"subject_status":"operating","subject_status_contradicts_page":true,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}