Wallet Guard / Consensys primary sources (2026-08-08)

Why this capture exists

This source snapshot supports a taxonomy cleanup rather than new intake. The useful question is no longer only what does the Wallet Guard browser extension do? but is Wallet Guard still best modeled as its own company boundary, or is the live legal / privacy / distribution shell now better represented by [[../companies/consensys]]?

Sources captured

• 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/wallet-guard-extension
• https://github.com/wallet-guard/wallet-guard-snap

Notes from sources

1) Wallet Guard homepage still frames the product as wallet-adjacent companion software

• Homepage says Wallet Guard is not a wallet and instead helps secure the user’s wallet of choice from web3 threats.
• Homepage FAQ says Wallet Guard cannot move assets or make decisions for the user.
• Homepage says transaction simulations currently support Ethereum, Polygon, Arbitrum, and Optimism, while phishing detection is blockchain agnostic.
• Homepage still presents the browser extension and optional security-dashboard flow as the practical user surface.

2) The Wallet Guard Snap keeps the product-layer distinction useful

• The Snap page and repo describe transaction simulation / human-readable transaction insights plus optional approval-reminder workflow.
• The Snap repo says the package was audited by Consensys Diligence.
• The Snap materials make the product distinction clear: browser-extension / Snap UX is still worth keeping separate from the broader company shell even if the entity boundary has shifted.

3) The legal / privacy perimeter now resolves to Consensys

• walletguard.app/privacy redirects to https://consensys.io/privacy-notice.
• walletguard.app/terms redirects to https://consensys.io/terms-of-use.
• Those redirects are strong evidence that the current legal and privacy boundary is not an independent Wallet Guard entity note but the broader Consensys company shell.

4) Chrome Web Store listing makes the operator boundary even clearer

• The listing includes a SUNSET NOTICE saying the Wallet Guard extension is being sunset soon and will no longer be supported.
• The listing names the developer as Consensys Software Inc..
• The listing links privacy and terms directly to Consensys, not to a separate Wallet Guard legal shell.
• That makes the current analytical split cleaner as project/product note under projects/ plus company/operator boundary under companies/consensys rather than a new standalone companies/wallet-guard note.

5) The extension repo still preserves the product mechanics worth keeping at project layer

• The extension repo describes proactive phishing protection using machine-learning checks for recently created domains, homoglyph translations, and impersonation attempts.
• The repo also explains that Wallet Guard proxies provider request / send methods to analyze transactions before handing unchanged requests back to the wallet.
• That is still a meaningful product-layer control surface, but it is not a stronger legal-entity boundary than Consensys.

Takeaway for taxonomy

• Keep wallet-guard as the product-layer note for browser-extension / Snap / transaction-insight mechanics.
• Do not promote Wallet Guard into its own company note on this pass.
• Use consensys for the current legal / privacy / distribution / support boundary.