Skip to main content
AVOID.NET
Sign in
← 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_revise · Fluid (Instadapp)
View on Solana ↗
Sequence
#3
Score
52 → 44 (-8)
Cluster
mainnet-beta
Slot
443512657
Off-chain at
2026-08-25T08:04:11.080Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
AHVT8TTrJUMaDSe1XNLBSyYp8xgzsBkdW6CQ27YeJd6e
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1314 chars)
{"actor":"judge","decided_at":"2026-08-25T08:04:10.844Z","decision":"review_revise","investigation_id":"e2cde9dd-d0ba-45e1-8daa-fb77b6e8957e","new_score":44,"page_slug":"fluid-instadapp","prev_score":52,"reason":"This page's account of Fluid's two 2026 security incidents and its history as a rebrand of Instadapp is well-supported by independent reporting and primary sources, and 15 of 24 checked claims were fully confirmed. However, the review disputes the page's total-funding figure of $24.5M (independently documented at $12.4M via Crunchbase, CoinDesk, and Tracxn), which appears twice on the page as effectively one repeated error, and it disputes the page's attribution of a December 2024 audit to Statemind when the actual December 2024 audit was performed by MixBytes. Several market figures (TVL, fees, revenue, circulating supply) are also stale relative to live data, and one of the page's own cited sources reports a materially lower bad-debt figure than the number the page presents, without acknowledging the discrepancy. None of these issues touch the core incident narrative, so the page is being sent back for revision rather than denied or delisted.","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}