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 · BFUSD
View on Solana ↗
Sequence
#2
Score
52 → 52 (0)
Cluster
mainnet-beta
Slot
443524608
Off-chain at
2026-08-27T07:08:48.343Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
FdTTCWWepr5JwMQEBdP98Ss29P2Mg2e9Bh3VDbfQEJQy
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1279 chars)
{"actor":"reviewer","decided_at":"2026-08-27T07:08:48.169Z","decision":"review","investigation_id":"da445d42-9342-4797-a1ed-1df8f09ac52a","new_score":52,"page_slug":"bfusd","prev_score":52,"reason":"The page's central and most important claim — that BFUSD is a reward-bearing margin asset and not a stablecoin — is well-supported directly by Binance's own blog and FAQ, and the page correctly avoids a mischaracterization that several of its own cited secondary sources (and CoinGecko itself) make. Legal/regulatory history, the UST-comparison controversy, and most yield/reserve figures check out against primary or credible secondary sources. Weaknesses include two dead links behind self-reported market-cap figures, one clearly wrong specific date (SEC dismissal timeline entry says May 1, 2025 vs. the actual May 29, 2025), a stale claim about USDC purchase support that Binance discontinued in August 2025, an uncited FTT comparison, and a collateralization-ratio claim framed as 'independently reported' when it in fact traces back only to Binance's own self-published dashboard with no independent audit or attestation behind it.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}