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 · Verus-Ethereum Bridge
- Sequence
- #2
- Score
- 8 → 8 (0)
- Cluster
- mainnet-beta
- Slot
- 422981710
- Off-chain at
- 2026-05-29T17:14:49.652Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- HtxDcmvT6pKm651oy4nMWRHpAUTenFTnpYH8XfqvBU3o
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1058 chars)
{"actor":"reviewer","decided_at":"2026-05-29T17:14:49.529Z","decision":"review","investigation_id":"6e148e7d-3998-498d-9b16-c35d8534284f","new_score":8,"page_slug":"verus-ethereum-bridge","prev_score":8,"reason":"The core factual claims about the exploit mechanics, asset amounts, attacker addresses, and technical root cause are well-sourced and confirmed across multiple credible outlets. The most significant accuracy problem is the page's claim that 'all stolen proceeds were subsequently moved through Tornado Cash,' which is disputed by contemporaneous sources and directly contradicted by the May 22, 2026 bounty recovery in which 75% of funds were returned to the Verus team. Three claims in the 'Team Response' section are stale, omitting the formal bounty deal and public statement issued by the Verus team on May 22. The Kelp DAO loss figure ($293M vs. the confirmed $292M) is a minor factual discrepancy.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}