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 · pNetwork
- Sequence
- #4
- Score
- 53 → 53 (0)
- Cluster
- mainnet-beta
- Slot
- 462278782
- Off-chain at
- 2026-10-28T00:46:54.224Z
- Anchored at
- 2026-10-28T00:47:19.000Z
- Block time
- 2026-10-28T00:47:19.000Z
Independent verification
- 1. Database (off-chain)
- 5ZPiWaXaUnKnfjFodnDy1FiPu8spDkk4hZcn73uNzBZw
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1486 chars)
{"actor":"judge","artifact_identity":"b7e6ce85925e14b332458f4bc8dceb95","band_override":null,"decided_at":"2026-10-28T00:46:53.941Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.5,"investigation_id":"26f2ef03-5f38-487a-86f0-3d1b056eb4f4","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":53,"page_slug":"pnetwork","prev_score":53,"reason":"Four of the eight reviewed claims (50%) were disputed or could not be verified, which falls in the significant-issues band. The key-leak root cause is credited to BlockSec in both the section text and the timeline (claim_findings[0], [1]), but the cited sources credit SlowMist. The claim that ZachXBT flagged pNetwork as high-risk has no supporting source, and its only citation is an unrelated pNetwork tweet (claim_findings[2], [3]). The core incident narratives (the 2021 hack, the pGALA drain, the lawsuit and the $50M compensation plan) match the sources. The penalty is set at the mild end of the band because the reviewer's confidence is low (0.5) and the errors are in attribution and one unsourced claim, not in the main events. The reviewer could not establish the project's current operating status, which is an open high-priority gap.","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}