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 · Penpie
- Sequence
- #3
- Score
- 28 → 20 (-8)
- Cluster
- mainnet-beta
- Slot
- 424291272
- Off-chain at
- 2026-06-04T17:44:52.525Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- D5sErTXPrZkVQkTCviPWgQ6twuSDbD3RBcW8qi5ciK8T
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1478 chars)
{"actor":"judge","decided_at":"2026-06-04T17:44:52.372Z","decision":"review_revise","investigation_id":"8388ccc1-df89-4f34-99e6-1bea24787247","new_score":20,"page_slug":"penpiexyz","prev_score":28,"reason":"The page is substantially accurate on all core facts — the exploit amount, mechanism, laundering timeline, law enforcement response, and compensation plan are confirmed by multiple credible sources including CoinDesk, The Record, and official governance documents. However, claim_findings[11] identifies a material omission in the audit section: the page attributes the pre-exploit audit gap to 'Zokyo and AstraSec,' but Rekt.news, official Penpie audit documentation, and the protocol's own GitHub identify WatchPug as one of the two early auditors alongside Zokyo — not AstraSec, which only reviewed the narrow May 2024 registration change. This mischaracterizes a high-severity section and is flagged as a high-priority coverage gap. Additionally, claim_findings[12] flags the Zokyo audit date of 2023-01-01 as an implausible placeholder given Penpie launched in June 2023, with the primary citation URL returning 404. Minor secondary issues include a terminology inconsistency on the compensation token name (SRT in news vs. PRT in governance documents) and a one-percentage-point discrepancy on the PENDLE token price drop.","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}