Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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
View on Solana ↗
Sequence
#5
Score
49 → 49 (0)
Cluster
mainnet-beta
Slot
464287586
Off-chain at
2026-11-02T00:06:25.659Z
Anchored at
2026-11-02T00:06:37.000Z
Block time
2026-11-02T00:06:37.000Z

Independent verification

1. Database (off-chain)
Gu634NHXxKXRxcj5eFjAdNebKhipqDjq8tiXXnwpQ1sj
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1832 chars)
{"actor":"judge","artifact_identity":"f57d70b4533aa5649640707cc24406e2","band_override":null,"decided_at":"2026-11-02T00:06:25.413Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4444,"investigation_id":"e5069dd4-353f-4479-86ef-a663685afdb3","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":49,"page_slug":"penpie","prev_score":49,"reason":"Of 9 claim findings, 3 were disputed (claim_findings[0], [1], [2]) and 1 was unverifiable (claim_findings[8]), giving 44% disputed, which falls in the significant band. The disputed items are all in the compensation section: the PIP #15 date (Nov 8, not Oct 7, 2024), the treasury share (3.5%, not 3%) and the token name (PRT, not SRT). The core incident facts (Sept 3, 2024 reentrancy exploit, about $27M, Singapore and FBI reports) were confirmed, and one cited CoinTelegraph URL is dead (claim_findings[7]). The page also presents Safupie as a live proposal when the cited source says it is on hold, and the current status and compensation outcome could not be established (high-priority coverage gap). Reviewer confidence is moderate (0.5), so the penalty sits in the lower half of the band and the page is not delisted.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":5,"severity_override":{"applied":true,"band":"significant","from_band":"significant","reason":"A material omission (Safupie put on hold and plan revised, per the cited PIP #15 page) is not covered on the page, so the verdict is judged by the significant band. This matches the band implied by the claim percentage; it does not make the verdict harsher than that band."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}