Cowrie Research

wallet-standard

3 min read

Wallet Standard

  • Name: Wallet Standard
  • URL: https://github.com/wallet-standard/wallet-standard
  • Category: chain-agnostic browser wallet-discovery and capability standard / injected-wallet coordination layer / anti-singleton interface infrastructure
  • Summary: Wallet Standard is browser wallet-discovery infrastructure, not a wallet SDK with a different logo. Its job is to replace singleton globals with shared registration, enumeration, and capability signaling so multiple injected wallets can coexist without the usual window.ethereum or window.solana turf war.
  • What it does:
    • Defines core Wallet and WalletAccount interfaces for injected wallets and the accounts they expose to apps
    • Standardizes how wallets register themselves and how apps enumerate available wallets through registerWallet and getWallets
    • Uses global browser events so apps can discover wallets already attached to the page and wallets that appear later
    • Pushes chain-specific functionality into extension namespaces rather than hard-coding one blockchain into the base interface
    • Publishes extension entry points for Bitcoin, Solana, and Sui, showing the base layer is intended to be multi-chain rather than Solana-only
    • Emphasizes versioned APIs, immutable byte-oriented inputs and outputs, multi-account support, and wallet-provided metadata like names and icons
  • Key claims:
    • The main repository README says Wallet Standard is a set of interfaces and conventions designed to improve wallet and application UX for any blockchain, which is the clearest reason to catalog it as chain-agnostic coordination infrastructure rather than a vendor-specific wallet API
    • The README exposes the project’s real primitives directly: Wallet and WalletAccount interfaces, global window events, wallet-side registerWallet, and app-side getWallets, which makes the standard’s control surface legible as discovery and registration rather than transport or custody
    • The design document says the standard exists to avoid fragile singleton globals like window.ethereum and window.solana, highlighting that the motivating problem is provider race conditions and wallet coexistence, not merely nicer typings
    • The design document explicitly says Wallet Adapter should be able to integrate the standard without breaking dapps, which matters because the project is trying to become a compatibility substrate under existing wallet-integration libraries rather than replace them all at once
    • The design principles say wallets should be stateless, isolated, and multi-tenant from the dapp’s perspective, which shifts authority away from wallet UI state and toward explicitly requested account and feature surfaces
    • The design document rejects a web3.js dependency and standardizes raw-byte interfaces, which is useful because it keeps the base interface portable across wallet implementations and avoids one SDK becoming the de facto control point
    • The extensions index and extension files show Bitcoin, Solana, and Sui namespaces living above one common base, reinforcing that the standard’s long-term significance is as a coordination layer for multi-ecosystem wallet discovery and capability negotiation
    • The Solana-specific companion repo says Solana behavior is an extension to the generic Wallet Standard rather than the standard itself, which is a useful architectural clue about where the maintainers think general discovery ends and chain-specific signing semantics begin
  • Whitepaper: No standalone Wallet Standard whitepaper or litepaper surfaced in this pass. The clearest current sources were the base repository README, design notes, extension index, extension documents, and the Solana extension repository materials collected in ../../whitepapers/wallet-standard-primary-sources-2026-05-08.md.
  • Sources:

Internal linkages

Graph View

Backlinks