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 · Taiko Ethereum L2 Bridge Exploit
- Sequence
- #2
- Score
- 15 → 15 (0)
- Cluster
- mainnet-beta
- Slot
- 443506715
- Off-chain at
- 2026-08-10T18:28:49.622Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- DfJWA8Aq4oZp7yW6fPWc1RtZQxinYhqztydiWooijZtm
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (956 chars)
{"actor":"reviewer","decided_at":"2026-08-10T18:28:49.448Z","decision":"review","investigation_id":"7c829a4d-1a89-4901-91bb-62f3cff14f24","new_score":15,"page_slug":"taiko-ethereum-l2-bridge-exploit","prev_score":15,"reason":"The page's core factual narrative — the June 22, 2026 Taiko bridge exploit, its ~$1.7M loss, the leaked SGX/Raiko signing key root cause, attack mechanics, and immediate response — is well corroborated by multiple independent tier-1/tier-2 sources and an uncited independent technical post-mortem. The one significant issue is that the 'Recovery Plan: PR #21820' section is factually stale: the PR was merged the day after it was opened and the bridge was fully restored with users made whole roughly a week and a half later, contradicting the page's framing of recovery as still pending.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}