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 · Core Lightning (CLN)
- Sequence
- #2
- Score
- 52 → 52 (0)
- Cluster
- mainnet-beta
- Slot
- 461976858
- Off-chain at
- 2026-10-27T06:55:52.773Z
- Anchored at
- 2026-10-27T06:56:24.000Z
- Block time
- 2026-10-27T06:56:24.000Z
Independent verification
- 1. Database (off-chain)
- Bm8WKHy3DQb7V3LtfMSMcGYwU5EMjySt7aAHVqYDX3HA
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1566 chars)
{"actor":"reviewer","artifact_identity":"635db73ed28a76030bba70a9bc5f06d8","decided_at":"2026-10-27T06:55:52.532Z","decision":"review","disputed_pct":0.3889,"findings_hash":"FYEiX8gvpbpiHTq5iSVxhypkV5JQnsGseaZ49e8tLkhP","investigation_id":"61a612f9-9887-4f5c-8afd-032e9ef11785","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":52,"omissions":{"material":1,"total":3},"page_content_hash":"a2e9a263b882be86dbdac6cc89d8589ff3f5bbb7908482ff49239d3e25d44982","page_slug":"core-lightning-cln","prev_score":52,"reason":"The core October 2026 narrative (active targeting of CLN v26.06.7 and earlier, v26.06.8 released Sept 22 with three bug classes, no confirmed losses as of Oct 2) is well supported. Problems: the rebrand date is wrong (March 31, 2022, not June 1), the August 26 'emergency advisory directing all operators offline' is contradicted by a cited-category source, the 2015 first-release and 'first implementation' claims and the Kimi K3 figures are not supported by the cited pages, and the advisory date is Oct 1 per some sources. The page is also stale: v26.06.9 (Oct 7) supersedes the 26.06.8 guidance. Several sources (TFTC August article, Cyber Kendra, shattered.io, section 4 context claims) were not fetched.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":2,"subject_status":"operating","subject_status_contradicts_page":true,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}