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 · BFUSD
View on Solana ↗
Sequence
#4
Score
40 → 40 (0)
Cluster
mainnet-beta
Slot
457991584
Off-chain at
2026-10-17T09:45:06.178Z
Anchored at
2026-10-17T09:45:30.937Z
Block time
—

Independent verification

1. Database (off-chain)
BtWCzvbMK2hWRUoMdN5dyq87QaCqdPhi922kHyCMRhNL
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2100 chars)
{"actor":"reviewer","artifact_identity":"ac8c6bc235368aac081ff3b43986ee5f","decided_at":"2026-10-17T09:45:05.928Z","decision":"review","disputed_pct":0.1714,"findings_hash":"DSpT6VXu6ZavTpyUhDYgEr8QKKfRNbCH9iy5tSN4KtZk","investigation_id":"da445d42-9342-4797-a1ed-1df8f09ac52a","mode":"findings_only","new_score":40,"page_content_hash":"0e6bef0cf0100ba1e66ace72a3861041808f74bede50b5fecaecc415e13b1cd8","page_slug":"bfusd","prev_score":40,"reason":"The page's core legal and financial history (the November 2023 DOJ guilty plea, $4.3B penalty, CZ's resignation and $50M personal fine, the February 2024 sentencing, and the May 2025 SEC civil-case dismissal) checks out against primary and independent sources, as do the main Jan 2025 reserve-fund and transparency figures ($7.2M USDT reserve, 760M circulation) and the August 2025 collateralization/APR figures. The most significant problem is a recurring, verifiable date error: the page states BFUSD was 'announced' on November 17, 2024, in three places (Product Overview, Operator Legal History framing, and the timeline), but that date was a third-party rumor/tweet, not Binance's own announcement, which Binance's own blog and The Block both date to November 26, 2024. Second, the page is stale on a structural point it could have caught from its own cited iq.wiki source: BFUSD migrated from an exclusive Binance-Futures product to Binance Simple Earn in August 2025 (dropping the futures-account requirement) and dropped USDC support shortly after, but the page still describes it in the present tense as 'exclusively' a Binance Futures product purchasable in USDT or USDC. Third, three of the lower-credibility market-cap citations (two 'self-reported market cap' articles and one timeline source) are dead links; the underlying $1.27B figure is corroborated elsewhere, but the $1.82B February 2026 peak could not be corroborated anywhere despite a thorough search and should be treated with caution.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}