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 · TAC Protocol Bridge
- Sequence
- #3
- Score
- 38 → 35 (-3)
- Cluster
- mainnet-beta
- Slot
- 423153675
- Off-chain at
- 2026-05-30T12:10:21.819Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- ECqdMVr5B2q1Q3qy9AAThsG7fQjWQevxuFV3Yvdggu73
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1340 chars)
{"actor":"judge","decided_at":"2026-05-30T12:10:21.649Z","decision":"review_approve","investigation_id":"4bd7b8fb-8444-4e3e-98d1-702adadd3e86","new_score":35,"page_slug":"tac-protocol-bridge","prev_score":38,"reason":"The page's core factual claims — the May 12 exploit, $2.86M amount, affected assets, Jetton wallet validation vulnerability, 10% white-hat bounty, 90% fund recovery, and May 14 reclassification — are consistently confirmed across multiple independent sources. The single disputed finding (claim_findings[16]) involves the stated all-time high of ~$0.028, which is contradicted by CoinMarketCap's recorded ATH of $0.04254, rendering the derived 25-32% post-exploit decline calculation inaccurate. This is a peripheral market data claim, not a core allegation about the exploit itself. Seven claims are partially supported due to single-source attribution for specific details (e.g., the 13 ETH + 300 ZEC bounty breakdown in claim_findings[7]) and editorial framing not directly sourced from TAC's own disclosures. Disputed percentage of 7.7% places the page within the approval band; the small negative delta reflects the incorrect ATH figure that should be corrected in revision.","score_delta":-3,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}