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_revise · Render Network
- Sequence
- #3
- Score
- 65 → 55 (-10)
- Cluster
- mainnet-beta
- Slot
- 424284457
- Off-chain at
- 2026-06-04T16:59:42.752Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 3AyBogXNMpcKHrqEWhaxXS4rdbhcrQ5BAJPzeqPPx9Gz
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1113 chars)
{"actor":"judge","decided_at":"2026-06-04T16:59:42.516Z","decision":"review_revise","investigation_id":"d8814204-c84a-49ff-b4f8-d8d55891c85f","new_score":55,"page_slug":"render-network","prev_score":65,"reason":"The page is substantially accurate on its core claims — the $30M fundraise, Solana migration, token economics, and partnership announcements are all well-supported by Tier 1 sources. The reviewer flagged one disputed claim (claim_findings[24]): the Upbit exchange hack date is stated as 'late 2024/early 2025' but multiple Tier 1 sources confirm it occurred November 27, 2025. Additionally, claim_findings[8] and claim_findings[16] carry citation mismatches where the cited source does not directly support its assigned claim, though the underlying facts are accurate. Two high-priority coverage gaps — on-chain treasury wallet analysis and the 2017-2018 ICO's regulatory/securities history — warrant expansion before the page should be considered complete.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}