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 · PiggyBank Protocol
- Sequence
- #5
- Score
- 52 → 52 (0)
- Cluster
- mainnet-beta
- Slot
- 457802352
- Off-chain at
- 2026-10-16T22:22:30.843Z
- Anchored at
- 2026-10-16T22:22:49.399Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 13J21bvD4e3rBV1Uc3WeL2YpvtHwwY5UNDu7ibdT9Qdq
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2381 chars)
{"actor":"reviewer","artifact_identity":"364189ca13ce6a2b3ae777d2783eb5cc","decided_at":"2026-10-16T22:22:30.302Z","decision":"review","disputed_pct":0.16,"findings_hash":"DU2wGyFyT3wTKTqqTFktSF9gV89MHu1h9KP3Nz8YzSSB","investigation_id":"4832d100-6f44-4d70-a8be-ebdc596fc278","mode":"findings_only","new_score":52,"page_content_hash":"ec855eab733d4357b18c4255405c0921bb2899effb6d8850e5742be6af651cdc","page_slug":"piggybank-protocol","prev_score":52,"reason":"The large majority of discrete, checkable claims on this page — the LAB basis-trade mechanics and dollar figures, the NAV drawdown percentages, ZachXBT's quotes and allegations about LAB's insider concentration and token-pump timeline, and the Drift Protocol hack details — were independently confirmed against multiple reputable outlets and, where possible, primary sources (e.g., TRM Labs' own blog for the Drift DPRK attribution). The most significant defect is a stale claim, repeated in three places (sections[1], sections[3], and timeline[8]), that PiggyBank's promised post-mortem report had not been published as of the investigation date: it was in fact published on or around June 10, 2026, with specific loss figures, well before the page's own cited sources were archived in late July 2026. A second notable defect, also appearing twice (sections[0] and sections[6]), is that the PDF linked as PiggyBank's 'audit report' is, on direct inspection, an unrelated Canva-made flyer rather than an audit document — the page's existing hedge language undersells this by framing it as a mere processability issue rather than a content mismatch. A minor overstatement was found in the 'both Dubai-based' characterization of the two LAB co-founders (only one is specifically placed in Dubai in the cited reporting), and the homepage user-count/performance figures could not be verified against the archived snapshot due to this reviewer's inability to access web.archive.org. One cited news URL (coincu.com) returned a server error on repeated fetch attempts. No accepted community submissions were present to review. Coverage gaps include the absence of any discussion of securities/regulatory risk for the tokenized-stock vaults and lack of independent on-chain verification.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}