Wallet Standard primary sources — 2026-05-08

Classification takeaway

Wallet Standard is best treated as browser wallet-discovery and capability-coordination infrastructure for injected wallets, not as a wallet product or a chain-specific adapter. Its key mechanism is a shared registration-and-discovery layer — wallet/account interfaces, global events, wallet-side registration, and app-side enumeration — that tries to end singleton-provider races while leaving chain-specific semantics to extension namespaces.

Primary sources reviewed

1. Base repository README — https://raw.githubusercontent.com/wallet-standard/wallet-standard/master/README.md

   • Best concise first-party framing of the project.
   • Useful for confirming the core primitives: Wallet, WalletAccount, window events, registerWallet, and getWallets.

2. Base repository landing page — https://github.com/wallet-standard/wallet-standard

   • Useful as a public project surface and cross-check for how maintainers describe the standard today.
   • Reinforces that the project is organized around common interfaces and discovery helpers rather than around one chain or wallet brand.

3. Design document — https://raw.githubusercontent.com/wallet-standard/wallet-standard/master/DESIGN.md

   • Important even though it is explicitly marked somewhat outdated.
   • Best source for the original intent: avoid singleton wallet globals, keep the interface chain-agnostic, decouple wallet UI state from dapp state, avoid a hard web3.js dependency, and standardize feature/version handling.

4. Extensions index — https://raw.githubusercontent.com/wallet-standard/wallet-standard/master/EXTENSIONS.md

   • Useful for showing that the base layer expects multiple ecosystems to define extensions above it.
   • Important classification clue because it turns the standard into a coordination substrate rather than a Solana-only convention.

5. Bitcoin extension entry — https://raw.githubusercontent.com/wallet-standard/wallet-standard/master/extensions/bitcoin.md

   • Useful for confirming the project already points to non-Solana downstream namespaces and feature sets.
   • Helps establish that the base layer is trying to generalize wallet discovery beyond one ecosystem.

6. Solana extension entry — https://raw.githubusercontent.com/wallet-standard/wallet-standard/master/extensions/solana.md

   • Useful for seeing how the generic base is specialized into Solana chains and signing features.
   • Important because it makes the split between base discovery and chain-specific capability namespaces explicit.

7. Sui extension entry — https://raw.githubusercontent.com/wallet-standard/wallet-standard/master/extensions/sui.md

   • Useful as another proof point that the base standard is being used as a cross-ecosystem coordination layer.
   • Helps avoid misclassifying the project as merely a Solana wallet initiative.

8. Solana extension repository README — https://raw.githubusercontent.com/anza-xyz/wallet-standard/master/README.md

   • Useful for confirming that the Solana repo positions itself as an extension to the base Wallet Standard.
   • Shows where maintainers expect chain-specific implementation work to live.

9. Wallet implementation guide — https://raw.githubusercontent.com/anza-xyz/wallet-standard/master/WALLET.md

   • Most useful practical source for the control surface.
   • Shows how wallet teams are expected to wrap existing APIs, register on the page, keep optional legacy globals for backward compatibility, and become legible to standard-compliant dapps.

Why it stays in the active corpus

• Strong comparison class for EIP-6963, CAIP-282, and other wallet-discovery standards that try to dislodge namespace capture.
• Useful non-Ethereum lens on where wallet-selection power migrates once discovery is standardized but metadata, feature namespaces, and selection libraries still mediate user choice.
• Helps connect browser discovery, capability negotiation, and later wallet-session standards into one control-surface map.