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_approve · Balancer
- Sequence
- #5
- Score
- 32 → 42 (+10)
- Cluster
- mainnet-beta
- Slot
- 426514946
- Off-chain at
- 2026-06-14T23:16:23.130Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 8iCxQ2z4f6gnTURRA5sULmGjmwJnKBGRo7VqKieRrzVZ
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1507 chars)
{"actor":"judge","decided_at":"2026-06-14T23:16:23.008Z","decision":"review_approve","investigation_id":"36f75834-67ae-4c11-b2be-78c9066f6778","new_score":42,"page_slug":"balancer","prev_score":32,"reason":"This is a severity-calibration review, not a fact-dispute review: all six claim_findings (indices 0-5) are supported with zero disputed claims. The reviewer (confidence 0.82) confirms Balancer is a legitimate, long-running DeFi AMM that was repeatedly victimized by external attackers rather than acting fraudulently. Three specific misattributions inflate the current score of 32 into an over-penalized band: the Velocore fork exploit ($6.8M) belongs to an independent protocol and not Balancer (claim_findings[2]); the Euler Finance $11.9M loss was cross-protocol collateral damage, not a Balancer contract flaw (claim_findings[1]); and the DNS/BGP hijack ($253K) targeted third-party registrar EuroDNS, overstating protocol-layer risk (claim_findings[1]). The page content stands as published and must remain live. The recommended score of 42 appropriately keeps Balancer in WARNING given the severity of the November 2025 $128M ComposableStablePool exploit and the March 2026 Balancer Labs corporate shutdown, without treating a suffered-by victim as a fraudulent entity. A positive delta of +10 corrects the band from 32 to the reviewer-recommended 42.","score_delta":10,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}