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 · Orca
View on Solana ↗
Sequence
#4
Score
80 → 80 (0)
Cluster
mainnet-beta
Slot
453834001
Off-chain at
2026-10-06T07:26:59.236Z
Anchored at
2026-10-06T07:27:34.162Z
Block time
—

Independent verification

1. Database (off-chain)
HY8np8zUTy2H6qqkUZ8uenTFQ8TDoNk7nPY9yeHKA5FU
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1880 chars)
{"actor":"reviewer","artifact_identity":"6f9745040ff031281313aeac4a51511b","decided_at":"2026-10-06T07:26:59.054Z","decision":"review","disputed_pct":0.0833,"findings_hash":"AfaE9Ku3MuR9f1Gh7fLL84S99rBNwrS28DMUz38UTcGQ","investigation_id":"06fdfbe1-7e9b-4a4f-8302-97f38657812a","mode":"findings_only","new_score":80,"page_content_hash":"3fc53941013c0fec2184ad0761e3e1619ac9ffafdd0127cd5bf0d6ca860159c5","page_slug":"orca","prev_score":80,"reason":"The page is well-sourced on Orca's audit history, funding round, governance mechanics, geo-block episode, and the Wavebreak launch, and these core claims checked out against primary and independent sources (GitHub, Immunefi, CoinDesk, The Block, Orca's own governance/X posts). The most significant problem is a scale metric: the page's claim of '$36 billion in cumulative trading volume' is contradicted by its own cited source (Solana Compass), which currently states Orca has processed roughly $500 billion cumulatively — an order-of-magnitude discrepancy that looks like a stale figure from early in Orca's history being presented as a current total. The TVL range ($400–500M) and the mid-2025 daily-activity snapshot are both now visibly stale relative to current live dashboard data, which shows substantially higher usage. Two citations have rotted: the direct Neodyme PDF link (404, unarchivable) and the dev.orca.so Account Architecture doc (redirects to a generic landing page); both have working replacements identified. The 'zero hacks since inception' claim is probably true but is partly supported by a mischaracterized citation (a CryptoRank piece actually about a different protocol's hack, which itself miscounts Orca's audits and names a different CEO than other sources).","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}