Wallet Guard

• Name: Wallet Guard
• URL: https://www.walletguard.app/
• Category: browser-extension wallet safety / transaction-preview companion tooling
• Tags: ethereum-ecosystem
• Summary: Wallet Guard is still worth keeping as a product note for browser-extension and Snap-level warning mechanics, but it no longer looks like the right place to promote a standalone company note. The sharper split now is product here, operator boundary in consensys: Wallet Guard still labels sites, previews transactions, and nags around approvals, while the current legal / privacy / distribution shell resolves to Consensys.
• What it does:
  • Runs a browser extension that flags phishing and suspicious sites targeting wallet users
  • Simulates transactions and shows a plainer read of likely asset movement before approval
  • Offers a MetaMask Snap that adds transaction insights and approval-reminder features inside the MetaMask flow
  • Proxies wallet-provider request paths in the extension so it can inspect transaction requests before returning them unchanged to the wallet
  • Publishes open-source extension and Snap code, which makes the product more inspectable than many closed companion tools
  • Now presents a sunset state at the extension-distribution layer: the Chrome Web Store listing says the Wallet Guard extension is being sunset soon and lists Consensys Software Inc. as the developer
• Key claims:
  • Homepage says Wallet Guard is not a wallet and instead helps secure the user’s wallet of choice from current web3 threats
  • Official FAQ copy says the extension does not connect directly to the user’s wallet or gain the ability to move assets, and that it simulates transactions without direct wallet interaction
  • Official site says transaction simulation currently supports Ethereum, Polygon, Arbitrum, and Optimism while phishing detection is blockchain agnostic
  • The extension repo describes multi-layered security via phishing protection and transaction analysis, including machine-learning checks for recently created domains, homoglyph attacks, and impersonation attempts
  • The extension repo also describes Wallet Guard as an intermediary that analyzes transaction requests and then returns them to the wallet without modification, which is the practical product-layer control surface worth preserving here
  • The Snap repo says the MetaMask Snap provides transaction insights and approval-revoking reminders and notes the package was audited by Consensys Diligence
  • walletguard.app/privacy and walletguard.app/terms now resolve to Consensys pages, and the Chrome Web Store listing identifies Consensys Software Inc. as the developer, so the current entity boundary is better modeled under consensys than as a new standalone companies/wallet-guard note
• Whitepaper: No classic whitepaper or litepaper is the point here. The useful current primary-source snapshot is ../whitepapers/wallet-guard-consensys-primary-sources-2026-08-08.md, which preserves both the product mechanics and the newer Consensys-side legal / distribution boundary.
• Sources:
  • https://www.walletguard.app/
  • https://www.walletguard.app/metamask-snap
  • https://walletguard.app/privacy
  • https://walletguard.app/terms
  • https://chromewebstore.google.com/detail/wallet-guard-protect-your/pdgbckgdncnhihllonhnjbdoighgpimk?hl=en
  • https://github.com/wallet-guard
  • https://github.com/wallet-guard/wallet-guard-extension
  • https://github.com/wallet-guard/wallet-guard-snap

Internal linkages

• Parent company / operator boundary: consensys.
• Best adjacent wallet-safety operator comparisons: blockaid and blowfish.
• Best signer-interpretation design companion: signer-intent-truth-security-object.

Protocol / company boundary

• Keep this note on the product-layer surface: browser extension behavior, phishing heuristics, provider-proxy transaction inspection, human-readable previews, and Snap-level approval-reminder workflow.
• Use consensys when the sharper question is who now controls the legal terms, privacy notice, distribution shell, and broader MetaMask-adjacent trust-and-safety packaging around Wallet Guard.
• That split is more useful than creating a new standalone companies/wallet-guard note, because the currently visible named operator boundary is already the broader Consensys shell.

Control surface

• At the product layer, authority sits in site labels, transaction-simulation quality, provider-proxy interpretation, warning thresholds, and how strongly the extension or Snap nudges approval behavior.

• At the company layer, the practical leverage now sits with Consensys through the legal/privacy perimeter, extension distribution, sunset decisions, and MetaMask-adjacent packaging.

• Treat Wallet Guard as browser-edge warning tooling inside a larger operator shell, not as the wallet, account system, or execution rail.

• Last reviewed: 2026-08-08 UTC