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 Protocol Ethereum Bridge
- Sequence
- #8
- Score
- 27 → 27 (0)
- Cluster
- mainnet-beta
- Slot
- 464284736
- Off-chain at
- 2026-11-01T23:56:10.951Z
- Anchored at
- 2026-11-01T23:56:28.000Z
- Block time
- 2026-11-01T23:56:28.000Z
Independent verification
- 1. Database (off-chain)
- EoYfsWGpopaytLSgT53ChAmZEFgJDMo7mbgLeHrGAuUJ
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1431 chars)
{"actor":"reviewer","artifact_identity":"66bc83b820e975f22129a55f8b0cde64","decided_at":"2026-11-01T23:56:10.847Z","decision":"review","disputed_pct":0.0909,"findings_hash":"HqSbggeG4hZo17MMUnvpbCbGGpwDStDFArDGxKTUyfA5","investigation_id":"25a63bee-d211-406a-87b5-7f88d5de2606","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":27,"omissions":{"material":0,"total":2},"page_content_hash":"04200a30d9b26499c6bebdd78b0cab55e3623d76efced15de64219677cf755b2","page_slug":"verus-protocol-ethereum-bridge","prev_score":27,"reason":"The core facts hold: two exploits (May 17-18 for about $11.58M, July 23 for about $7.54M), the shared bug class, the 4,052.4 ETH return for a 1,350 ETH bounty, the July 8 redeposit, and the lack of an official post-mortem all match The Block, Merkle Science and Rekt. Corrections needed: the summary overstates the redeposit (only about 1,192 ETH was reloaded), the Tornado Cash timing is relative to PeckShield's report rather than the attack, and the TVL figure differs from Rekt's DefiLlama-based number. Several sources were not fetched, which limits scope.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":8,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}