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 · Payy Network
- Sequence
- #2
- Score
- 28 → 28 (0)
- Cluster
- mainnet-beta
- Slot
- 461980364
- Off-chain at
- 2026-10-27T07:08:25.153Z
- Anchored at
- 2026-10-27T07:08:50.000Z
- Block time
- 2026-10-27T07:08:50.000Z
Independent verification
- 1. Database (off-chain)
- FLh8FuRLKmwNyrTYmTx1KaekS9k31HTkuKcUdzj63RDy
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1521 chars)
{"actor":"reviewer","artifact_identity":"cbe40b8bac2def812bb619a7d61258c6","blocked_count":1,"decided_at":"2026-10-27T07:08:24.841Z","decision":"review","disputed_pct":0.3636,"findings_hash":"HnJ65M27JNHEFH8RdnDkuJPH5FJWG1E8sS4fmXw3sxLg","investigation_id":"acfcb1c5-d03f-4e67-ae2f-60e8a37a8d1c","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":28,"omissions":{"material":0,"total":1},"page_content_hash":"3724ed08e5333d5ad204eae5358abd0d033a0ff569f96b86bc15c03e01045d69","page_slug":"payy-network","prev_score":28,"reason":"The core incident is well supported: the exploit date, amounts, two-transaction pattern, swap to ETH, absence of a key compromise, and the halted network. Errors found: the halt is dated Sept 25 where sources say Sept 24, and the ten-month intervals do not match the page's own dates (about 6.5 months from pin to patch, about 11 months from pin to exploit). The technical root cause and version details rest on a single third-party GitHub issue rather than Payy's own post-mortem. The CVE section probably describes the same issue as the June 2026 disclosure. The user and country counts are unchecked because FinSMEs returned 403.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":11,"sequence_num":2,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}