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 · Keep3r Network
- Sequence
- #4
- Score
- 58 → 58 (0)
- Cluster
- mainnet-beta
- Slot
- 464277277
- Off-chain at
- 2026-11-01T23:29:31.092Z
- Anchored at
- 2026-11-01T23:29:56.000Z
- Block time
- 2026-11-01T23:29:56.000Z
Independent verification
- 1. Database (off-chain)
- A8YexdymC6KjzsA4g5FmUAfzPtqsMGfaVuHtHgJodY2w
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1364 chars)
{"actor":"judge","artifact_identity":"cadff0ebe39d2c195353a7b1d27baa98","band_override":null,"decided_at":"2026-11-01T23:29:30.849Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2222,"investigation_id":"1d044334-6ce9-4740-ac25-afeca016050a","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":58,"page_slug":"keep3r-network","prev_score":58,"reason":"Of 9 claim findings, 2 were unverifiable (22%), which falls in the minor-issues band. The core incident narrative (the June 2023 exploit and the Statemind disclosure) was supported by primary sources. However, the only cited source for the 2023 exploit returns 404 (claim_findings[2], [3]), and the summary's ZachXBT claim has no support on the page or in search (claim_findings[0]). The timeline overstates the SEC's interest in Keep3r (claim_findings[6]), and the 2025 market data is out of date (claim_findings[7]). The penalty sits in the upper part of the band because of the dead citation and the unsupported claim. It is limited because reviewer confidence is only 0.5 and many cited sources were not fetched.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}