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 · Ethena
- Sequence
- #3
- Score
- 38 → 58 (+20)
- Cluster
- mainnet-beta
- Slot
- 426514504
- Off-chain at
- 2026-06-14T23:16:00.120Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- AVeomZ9XZ2uFezeuPcfoytT65aURBewjHCHbv6LQeKrm
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2012 chars)
{"actor":"judge","decided_at":"2026-06-14T23:16:00.013Z","decision":"review_approve","investigation_id":"325d327c-4f88-4c31-abb2-987378d35669","new_score":58,"page_slug":"ethena","prev_score":38,"reason":"The reviewer's blue-chip calibration found 0% disputed claims across all 6 findings — the page content is accurate and stands as published. The miscalibration lies in the trust score band, not the facts. Three specific framing problems drive the over-penalty: claim_findings[1] shows the page uses a $0.65 Binance price as a structural failure signal while its own cited CoinDesk source explicitly concluded 'No, Ethena's USDe Didn't De-peg' — the event was Binance-specific infrastructure failure during a record $19B liquidation cascade; claim_findings[2] shows both the Discord hack and domain registrar compromise were third-party social engineering attacks with no protocol-level funds affected; and claim_findings[3] shows the insider farming allegations were fully retracted by the accuser. The BaFin enforcement action (claim_findings[0]) is real, material, and correctly documented — but the winding-up order was revoked August 2025 after completion of redemptions, the entity contested and exited the German subsidiary cleanly, and this represents regulatory compliance friction under a new EU framework rather than fraud. The structural risks of the delta-neutral model, counterparty concentration, and reserve fund adequacy are genuine and well-disclosed on the page, justifying a CAUTIONARY rating. The protocol is institutionally backed (BlackRock BUIDL, Kraken custody, Series B), carries $4.5-6B TVL, and has engaged the SEC Crypto Task Force directly (claim_findings[4]). Score 38 (WARNING) is calibrated for elevated fraud or loss risk; score 58 (CAUTIONARY) reflects genuine structural risk with legitimate operations — a +20 delta is warranted.","score_delta":20,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}