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 · Verus-Ethereum Bridge
- Sequence
- #3
- Score
- 8 → 0 (-10)
- Cluster
- mainnet-beta
- Slot
- 422981716
- Off-chain at
- 2026-05-29T17:14:49.717Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 5mWaAiULV3jFaXRXYYHtWW5FL4ai941ne7gVjjfR4Dom
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1470 chars)
{"actor":"judge","decided_at":"2026-05-29T17:14:49.529Z","decision":"review_revise","investigation_id":"6e148e7d-3998-498d-9b16-c35d8534284f","new_score":0,"page_slug":"verus-ethereum-bridge","prev_score":8,"reason":"The core exploit facts — attack date, asset amounts, attacker addresses, technical root cause in checkCCEValues, and Blockaid detection — are confirmed across multiple credible sources including Tier 1 outlets and Halborn's post-mortem. However, claim_findings[17] (sections[2]) is explicitly disputed: the page states 'all stolen proceeds were subsequently moved through Tornado Cash,' but contemporaneous sources show funds were not yet laundered at reporting time, and by May 22, 2026 approximately 75% of funds (4,052 ETH) were returned to the Verus team via a negotiated bounty deal. This overstatement is corroborated in the summary section as well (claim_findings[3], partially_supported). Additionally, four claims are stale — all concentrated in the 'Team Response' section — because the page repeatedly asserts the Verus team issued no public statement and no bounty existed, both of which are directly contradicted by documented May 22 events. These gaps are rated high-priority by the reviewer. The Kelp DAO figure ($293M vs confirmed $292M) is a minor numerical inaccuracy. No link rot was found.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}