Blowfish

• Name: Blowfish
• URL: https://blowfish.xyz/
• Category: wallet security middleware / transaction-simulation and dapp-risk infrastructure / blocklist distribution
• Summary: Blowfish is wallet-side trust-and-safety middleware. The useful read is not security badge for wallets. It is the control plane for domain classification, signing previews, blocklist distribution, overrides, and sometimes even privacy-preserving proxy placement.
• What it does:
  • Offers a wallet-facing trust-and-safety platform that scans domains, dapps, transactions, and signing flows before the user approves them
  • Aggregates Blowfish’s own intelligence with outside risk-signal sources rather than relying on one internal blacklist only
  • Publishes a local blocklist library that lets integrators fetch a blocklist object and bloom filter, rescan domains locally, set priority allow / block lists, and persist local overrides
  • Recommends frequent blocklist refreshes and makes the distribution and freshness layer explicit instead of hiding it behind one hosted API
  • Publishes a simple reverse-proxy image so wallet teams can hide user IP addresses from Blowfish and avoid exposing API keys to client apps
  • Open-sourced the now-deprecated Blowfish Protect frontend stack, which exposed extension UX, backend, transaction portal, and shared frontend packages as separate layers
• Key claims:
  • The homepage presents Blowfish as a trust-and-safety platform for wallets rather than as a single phishing list or one-off simulation widget
  • The local blocklist package makes policy distribution visible: wallets can pull a blocklist plus bloom filter, apply their own priority lists, cache updates, and locally allow a blocked domain after explicit user action
  • The simple-proxy repo exposes a second real control surface: some integrators do not want end-user IP addresses or raw API keys flowing straight to the provider
  • Public materials show Blowfish covering both static domain reputation and transaction-signing review, which makes it broader than a browser blacklist note
  • The deprecated but open Blowfish Protect monorepo is still analytically useful because it separates the UX, backend, and shared-package layers cleanly
• Whitepaper: No standalone whitepaper or litepaper surfaced in this pass. The strongest primary materials were the official homepage and Blowfish’s public GitHub repositories, collected in ../whitepapers/blowfish-primary-sources-2026-05-14.md.
• Sources:
  • https://blowfish.xyz/
  • https://github.com/blowfishxyz
  • https://raw.githubusercontent.com/blowfishxyz/blocklist/main/README.md
  • https://github.com/blowfishxyz/simple-proxy
  • https://raw.githubusercontent.com/blowfishxyz/blowfish-frontend-monorepo/main/README.md

Internal linkages

• Best comparisons: blockaid and hypernative.

Control surface

• The leverage sits in feed selection, blocklist freshness, override policy, proxy placement, and how aggressively an integrator turns a warning into a stop.

• None of that is onchain. Blowfish is an interpretation layer in front of wallets and dapps.

• Treat it as trust-distribution infrastructure, not as a wallet and not as a protocol.

• Last reviewed: 2026-05-25 UTC