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_revise · Taiko Ethereum L2 Bridge
- Sequence
- #3
- Score
- 18 → 10 (-8)
- Cluster
- mainnet-beta
- Slot
- 443506743
- Off-chain at
- 2026-08-10T18:40:26.375Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 6iiip3h2KWAMQLnDWxcj6v9WPhTEuxCveuMamrtREYJr
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1508 chars)
{"actor":"judge","decided_at":"2026-08-10T18:40:26.191Z","decision":"review_revise","investigation_id":"e7571a21-62a4-49e5-af98-83b7f5b14098","new_score":10,"page_slug":"taiko-ethereum-l2-bridge","prev_score":18,"reason":"The page's core facts about the June 22, 2026 Taiko bridge exploit — loss amount, contract addresses, root cause (leaked SGX signing key), attack mechanics, and market impact — are well corroborated by independent tier-1/tier-2 sources, with a disputed rate of 8.3% (claim_findings summary). However, the review found the Recovery Plan section (claim_findings[7]) to be materially stale: it presents recovery PR #21820 and bridge reopening as unresolved, when in fact the PR merged the next day and the bridge fully reopened on July 2, 2026 with users made whole and TAIKO up 136% — a resolution that predates the page's own newest cited sources. The review also flags a mischaracterization of the Ledger CTO's comments (claim_findings[3]), which omitted his architectural-design criticism alongside the operational-error framing, and identifies a high-priority coverage gap: this page substantially duplicates another corpus entry on the same incident. These are update/completeness issues rather than disputes of the underlying facts, so the page is not denied, but it needs a revision pass before it reflects the current state of the story.","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}