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_approve · Payy Network
- Sequence
- #11
- Score
- 32 → 32 (0)
- Cluster
- mainnet-beta
- Slot
- 465106165
- Off-chain at
- 2026-11-04T00:49:00.956Z
- Anchored at
- 2026-11-04T00:49:27.000Z
- Block time
- 2026-11-04T00:49:27.000Z
Independent verification
- 1. Database (off-chain)
- GGha8dtGDUFNrsFubKhwyszLbf9NjjvAJV8Z1CHCdqYh
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1254 chars)
{"actor":"judge","artifact_identity":"7d064a1627a51fe9cc93d789c65a6919","band_override":null,"decided_at":"2026-11-04T00:49:00.608Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"acfcb1c5-d03f-4e67-ae2f-60e8a37a8d1c","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":32,"page_slug":"payy-network","prev_score":32,"reason":"All 8 checked claims (claim_findings[0-7]) were confirmed against their cited sources, including the drain figures and timing, the CVE-2026-48100 details from a Tier 1 record, and the secondhand claims-process reporting, so disputed_pct is 0%. The page already says the cause is unconfirmed and that the compensation reporting is secondary. The wallet-closure omission is minor and covered in the body, and the reported shutdown status matches the page. The high-priority gap, that Payy's own post-mortem is missing, suggests expansion rather than correction, because the page labels those points as secondhand.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"sequence_num":11,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}