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 · Keep3r Network
- Sequence
- #3
- Score
- 58 → 58 (0)
- Cluster
- mainnet-beta
- Slot
- 464277272
- Off-chain at
- 2026-11-01T23:29:30.913Z
- Anchored at
- 2026-11-01T23:29:54.000Z
- Block time
- 2026-11-01T23:29:54.000Z
Independent verification
- 1. Database (off-chain)
- J5VysvvgHdg1W6UbsFG4Cur2fCXR2PC9MYk7yHv5vmSM
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1358 chars)
{"actor":"reviewer","artifact_identity":"cadff0ebe39d2c195353a7b1d27baa98","decided_at":"2026-11-01T23:29:30.849Z","decision":"review","disputed_pct":0.2222,"findings_hash":"AzT5S2q8Va6YGyQVUo5hGob4qt7AkoLQ5knfPNPPe2Pd","investigation_id":"1d044334-6ce9-4740-ac25-afeca016050a","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":58,"omissions":{"material":0,"total":1},"page_content_hash":"32cb18873cf853714109a0b56314eb8eb8d747f949f44c96692c9db93deb5ec7","page_slug":"keep3r-network","prev_score":58,"reason":"The incident narrative (June 2023 vanity-address exploit, Statemind GaugeProxyV2 disclosure, SEC context) is largely supported by the sources I checked. Problems found: the DAO Times link used for the 2023 exploit is a 404, the summary's ZachXBT claim has no support anywhere on the page or in search, the timeline overstates the SEC's Keep3r focus, and the market data appears stale. Spirit Swap was not found in the PR Newswire release. Coverage was partial because many cited sources were not fetched.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}