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 · Treasure DAO
- Sequence
- #5
- Score
- 34 → 34 (0)
- Cluster
- mainnet-beta
- Slot
- 424139615
- Off-chain at
- 2026-06-04T00:57:55.546Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- HhuU9kcQCNVnnS7pf89uiwbMhgcWa3hWg2GoRSZymC6N
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1361 chars)
{"actor":"judge","decided_at":"2026-06-04T00:57:55.285Z","decision":"review_approve","investigation_id":"3237b462-d3c5-42b9-9b44-d2611221db93","new_score":34,"page_slug":"treasure-dao","prev_score":34,"reason":"The reviewer evaluated 27 claims and found zero directly disputed by credible counter-evidence, yielding a disputed_pct of 3.7%. All core allegations — the March 2022 exploit mechanism (claim_findings[1]–[7]), the 2025 financial figures (claim_findings[15]–[17]), and the Treasure Chain shutdown (claim_findings[20]) — are confirmed by independent sources including a Tier 1 SlowMist security report and the project's own governance forum. The five partially-supported findings (claim_findings[0], [8], [10], [12], [14], [22]) reflect minor precision gaps: a missing third co-founder name, an imprecise NFT return count, a date off by one quarter, and a paraphrased rather than direct quote. One claim (claim_findings[19]) is unverifiable due to a 403 response on the primary source, but the underlying substance is corroborated by other confirmed facts on the page. No coverage gaps are rated high priority. These weaknesses merit editorial correction but do not undermine the factual integrity of the page.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}