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 · PrismaLST
View on Solana ↗
Sequence
#4
Score
55 → 55 (0)
Cluster
mainnet-beta
Slot
464447529
Off-chain at
2026-11-02T09:37:36.853Z
Anchored at
2026-11-02T09:37:39.000Z
Block time
2026-11-02T09:37:39.000Z

Independent verification

1. Database (off-chain)
5iVKqXHyH1uv813QjqtR2FDVbsg4WKAYubcpaP5PapzS
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1780 chars)
{"actor":"judge","artifact_identity":"794c9109141265cafd8a7ab6c9682ef4","band_override":null,"decided_at":"2026-11-02T09:37:36.613Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3333,"investigation_id":"3dce0aa8-69c3-4cb1-9c80-b11a0b3c6b92","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":55,"page_slug":"prismalst","prev_score":55,"reason":"The core exploit facts (timing, pause time, attacker address and the 3,479 ETH total loss) match the official post-mortem (claim_findings[0-2]). Three of nine claims could not be verified (the flash loan amount, the DAO vote percentage and the ZachXBT legal-proceedings claim, claim_findings[3, 7, 8]), which puts the unverified share at about 33%. The 'pre-exploit peak' TVL framing is doubtful and the current TVL figure could not be checked (claim_findings[6]). The page also omits the shutdown proposal and Resupply migration and the user reimbursement plan, both rated material. Because reviewer confidence is moderate and no core allegation was disputed, the penalty is set in the lower-middle of the significant band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"severity_override":{"applied":true,"band":"significant","from_band":"significant","reason":"The review reports two material omissions (the PIP-46 shutdown proposal and Resupply migration, and the DAO user reimbursement plan) and says the page's current-state picture is contradicted. The page's silence on the wind-down changes how readers interpret the low TVL, so the page is judged in the significant band."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}