Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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 · OlympusDAO
View on Solana ↗
Sequence
#2
Score
28 → 28 (0)
Cluster
mainnet-beta
Slot
443520296
Off-chain at
2026-08-26T11:13:33.867Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
9r9stoRTbZuPn5RrY9SrXvqewKuh5oDezDaTgHHbUSYN
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1261 chars)
{"actor":"reviewer","decided_at":"2026-08-26T11:13:33.728Z","decision":"review","investigation_id":"d4a96a3a-5e0d-4789-85c3-1d88ae66379d","new_score":28,"page_slug":"olympusdao","prev_score":28,"reason":"Most discrete, checkable facts on the page (launch details, price/TVL/market-cap figures, the Wonderland/0xSifu episode, the Liang lawsuit's initial allegations, the Bond Protocol exploit and same-day fund return, and the CFTC/Ikkurty ruling) are independently corroborated by credible sources. The page's current-state description (Cooler Loans/RBS) correctly reflects the protocol's 2026 mechanics rather than a stale 2021-era model, and it does not understate the Bond Protocol exploit's remediation. However, it conflates market cap with TVL when claiming 'billions in TVL,' overstates the ATH-to-current drawdown as 'more than 99%' by selecting the larger of its own two cited ATH figures, mischaracterizes a 2023 lawsuit filing as continuity of a 2022 case that had actually been voluntarily dismissed, and omits the much larger April 2022 Rari Fuse hack that directly affected OlympusDAO's own treasury pool.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}