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 · Blur Finance
View on Solana ↗
Sequence
#4
Score
2 → 2 (0)
Cluster
mainnet-beta
Slot
457816582
Off-chain at
2026-10-16T23:14:12.415Z
Anchored at
2026-10-16T23:14:19.421Z
Block time
—

Independent verification

1. Database (off-chain)
822GEn3VDTRVkVJ754RS9C9cUk1pee8Tvd3eSgmNR4Ww
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2290 chars)
{"actor":"reviewer","artifact_identity":"57b6de8ee20ca6d632f58ab922ee541f","decided_at":"2026-10-16T23:14:12.235Z","decision":"review","disputed_pct":0.35,"findings_hash":"Dydw4eFkdM4MLFZNa58fPT1U1KXJ939uNweRTRudA7uW","investigation_id":"5885afbd-3fec-4be4-a732-12b9cfb3e382","mode":"findings_only","new_score":2,"page_content_hash":"1b852efb2db18dc3fef1e3bc8a73ec52883624a2b343d71e0cad8f05d9a504bd","page_slug":"blur-finance","prev_score":2,"reason":"The core narrative — a ~$600,000 rug pull from the BLR yield-aggregator protocol across BNB Chain and Polygon in August 2022, developer disappearance, 99% token collapse, and PeckShield's public flagging — is well supported by multiple independent, credible news sources (CoinDesk, CryptoSlate, IBTimes, TronWeekly) that were successfully fetched and cross-checked. Team-verification claims (ICOholder's 0% verification rate) and the contemporaneous Dragoma/Teddy Doge rug pulls are also independently confirmed. However, the page contains a significant, repeated factual error: it attributes a June 2022 Dedaub smart-contract security audit to the rug-pulled BLR protocol in three separate places (Protocol Overview, Scam Pattern and Red Flags, and the timeline), when the cited Dedaub report is actually an audit of the unrelated, legitimate NFT marketplace Blur (blur.io) — the very entity the page's own Disambiguation section says is a different project. This is a materially misleading conflation given the audit is used as evidence of either legitimacy-window-dressing or a scam red flag. Additionally, one cited Hacken source URL is dead (404) and could not be confirmed to say what the page attributes to it, and several precise on-chain figures (BscScan/PolygonScan transaction counts, balances, and the 'Fake_Phishing438' label) could not be independently verified because both block explorers return 403 to automated fetch tools and the cited wayback archive snapshots are unreachable from this environment — these are flagged unverifiable rather than disputed. A claimed 'July 2023 Dedaub audit of Exchange V2' for the NFT marketplace could not be located in available audit indices.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}