Browser Wallet

Overview

A browser wallet can be self-custodial, custodial, or connected to a separate signing device. Some store encrypted keys within browser storage, some expose an account managed by a provider, and others act only as an interface to hardware or mobile wallets.

This term is broader than browser extension wallet. The security model depends on where keys are held and how websites obtain permission. Phishing pages, injected scripts, compromised dependencies, session theft, and confusing chain or account prompts can affect browser-based use even when private keys never leave a secure device.

Users should identify the actual custody and signing model, use verified URLs or software, review permissions, and keep large reserves separate from routine web activity. Developers should isolate origins, minimize stored secrets, protect sessions, and present meaningful signing details. Browser access describes the interface, not the level of custody or security.

Material risks for Browser Wallet include credential compromise, malicious destinations, unsupported assets, wrong-network transfers, stale balances, compromised software, provider outage, privacy leakage, and inaccessible recovery material. For Browser Wallet, controls should reflect value, automation, reversibility, and whether the organization or a third party controls signing.

Browser Wallet should be distinguished from the asset balance and from the application that displays it. For example, a customer-facing success message does not prove that the intended transaction executed on the correct network; operations should verify execution and reconcile the result before irreversible fulfillment.

Production ownership for Browser Wallet should identify the user or legal entity, supported assets and networks, address model, custody boundary, signing authority, recovery method, and systems permitted to request or observe transactions. For Browser Wallet, these fields determine who can act and which evidence is authoritative.