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 · Zabu Finance
View on Solana ↗
Sequence
#5
Score
50 → 50 (0)
Cluster
mainnet-beta
Slot
457825073
Off-chain at
2026-10-16T23:44:21.814Z
Anchored at
2026-10-16T23:44:52.978Z
Block time
—

Independent verification

1. Database (off-chain)
DXp6Q6qZe8Bq72YWEn7gwVLkvpBQ4KDMXC2ssT8bGo2T
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1786 chars)
{"actor":"reviewer","artifact_identity":"21bc5dbecda6c571fe3f03f2ba5e5932","decided_at":"2026-10-16T23:44:21.181Z","decision":"review","disputed_pct":0.5,"findings_hash":"BR4ovtmrjEUPGUDotcsL1xJGpKvH4SY2tq4cmLyjXdWw","investigation_id":"165277a4-bd68-46b8-92c0-11ffcadf8ec3","mode":"findings_only","new_score":50,"page_content_hash":"63912d75e7e516840b6628bcecde93e2960957cb16b8dcd6242b68c01400b994","page_slug":"zabu-finance","prev_score":50,"reason":"The core incident narrative — date, dollar amount, attack mechanism (fee-on-transfer SPORE token accounting flaw), the PolyYeld precedent, and the team's snapshot/v2 recovery plan — holds up well against Halborn, CoinDesk, and Quadriga Initiative's technical writeups. Two clear defects were found: the 'ZachXBT flag' section asserts a specific, unsupported fact (that ZachXBT flagged this project) citing only a Wikipedia article that never mentions Zabu Finance, and no independent corroboration could be found; and the token-price-collapse section attributes a quote and a 25% recovery figure to 'Cointelegraph,' when the 25% figure actually traces to AMBCrypto (which the section does cite) and Cointelegraph is not cited anywhere on the page. Several other claims (SSL certificate expiry, current DefiLlama TVL, Coinbase/Binance delisting, exact burn valuation) could not be independently confirmed because the relevant live pages returned 403s and web.archive.org was not reachable from this environment; these are marked unverifiable rather than disputed. The page has no on-chain fund-tracing or law-enforcement-response coverage, which would strengthen a hack-focused investigation.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}