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 · Payy Network — Noir/Barretenberg Verifier Flaw Post-Mortem
- Sequence
- #4
- Score
- 37 → 37 (0)
- Cluster
- mainnet-beta
- Slot
- 462170619
- Off-chain at
- 2026-10-27T18:23:07.915Z
- Anchored at
- 2026-10-27T18:23:16.000Z
- Block time
- 2026-10-27T18:23:16.000Z
Independent verification
- 1. Database (off-chain)
- Hx9QgTNgHhns9ZHYeL4cYoL8DEGBigj5UDMZ3C15dcS1
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1818 chars)
{"actor":"judge","artifact_identity":"12ead607b46e24ec2d50810cf9becaab","band_override":null,"decided_at":"2026-10-27T18:23:07.599Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3846,"investigation_id":"4bac3cd6-8c34-406c-86f0-9ffb2e61b883","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":37,"page_slug":"payy-network-noir-barretenberg-verifier-flaw-post-mortem","prev_score":37,"reason":"Of 13 claims checked, 5 were disputed or could not be verified (about 38%). The disputed items concern the GitHub advisory date: the advisory itself says June 10, 2026, not September, so the page's suggestion that the June date is an aggregator artifact is unsupported (claim_findings[4], [5], [6]). The SpendNode-sourced commit and release details were not found in the cited article (claim_findings[2], [3]). The page is also out of date on reimbursement, and it omits the 30-day claims window and the planned shutdown of Payy Wallet (claim_findings[9], [10]; omission_findings[0]). The core incident figures and Payy's initial statements were confirmed, and the reviewer's confidence was moderate, so the penalty sits in the middle of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"severity_override":{"applied":true,"band":"significant","from_band":"significant","reason":"The review reports a critical omission (Payy's October 2026 claims window and planned Payy Wallet shutdown) and subject_status.contradicts_page is true. The percentage band is already significant, so the override holds the verdict at the significant band rather than moving it harsher."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}