Skip to main content
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 · BFUSD
View on Solana ↗
Sequence
#3
Score
5240 (-12)
Cluster
mainnet-beta
Slot
443524611
Off-chain at
2026-08-27T07:08:48.455Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
736oaC7VeGgkoN5h6YM84636LiLRzjLCcHAsmiBqLzFL
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1865 chars)
{"actor":"judge","decided_at":"2026-08-27T07:08:48.169Z","decision":"review_revise","investigation_id":"da445d42-9342-4797-a1ed-1df8f09ac52a","new_score":40,"page_slug":"bfusd","prev_score":52,"reason":"The review checked 22 factual claims on the BFUSD page: 12 confirmed, 3 partially supported, 3 unverifiable, 1 disputed, 1 outdated, and 2 backed only by dead links. That puts roughly 18% of claims in the disputed-or-unverifiable category, which calls for revisions rather than approval or removal. On the plus side, the page's most important claim -- that BFUSD is a reward-bearing Binance Futures margin asset and not a stablecoin -- is directly confirmed against Binance's own blog and FAQ, correctly departing from several of the page's own secondary sources (OKX, CoinGecko, Cryptopolitan) that mislabel it. Set against that, the page describes its ~100.86% collateralization ratio as 'independently reported' when it in fact traces only to Binance's own self-published transparency dashboard, with no independent audit or attestation behind it -- a mischaracterization of the product's central risk figure, and a high-priority gap the reviewer flagged directly. The page also gives an incorrect date for the SEC's dismissal of its Binance case (May 1, 2025, versus the actual May 29, 2025), presents USDT/USDC purchase support as current when Binance discontinued USDC for BFUSD on August 25, 2025, cites two now-dead links behind self-reported market-cap figures, and draws an uncited comparison between BFUSD and FTX's collapsed FTT token. None of this undermines the page's core narrative, but together the errors and provenance issues warrant a moderate score reduction and revision rather than a clean pass.","score_delta":-12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}