wallets

Implement EIP-6963 wallet connection flows with deep linking and WalletConnect fallbacks.

7|3|Updated Mar 3, 2026

Search Tags:#wallet #session-persistence #wallet-connect #embedded-wallet #eip-6963 #mobile-deep-linking #walletconnect-v2

Ready to run

npx skills add https://github.com/konopkja/ethux-design --skill wallets-konopkja

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wallets
Source: https://github.com/konopkja/ethux-design/tree/main/skills/wallets
Command: npx skills add https://github.com/konopkja/ethux-design --skill wallets-konopkja

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Wallet connections in Ethereum dApps are fragmented across providers, devices, and flow patterns, leading to confusing UX, inconsistent states, and missed onboarding opportunities.

Core Features & Use Cases

EIP-6963 multi-wallet discovery and seamless connect flows
Mobile deep linking for wallet apps and universal links
Session persistence and auto-reconnect to reduce re-auth prompts
Embedded/smart wallets for new users with upgrade paths
WalletConnect v2 fallback with QR and mobile deep linking
Clear error states, ENS/name resolution guidelines, and disconnect/reconnect flows

Quick Start

Implement a wallet connection flow using EIP-6963 with mobile deep linking and WalletConnect fallback.

Frequently Asked Questions about wallets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I implement EIP-6963 multi-wallet discovery in my dApp?▼

EIP-6963 multi-wallet discovery allows dApps to detect multiple installed wallet extensions simultaneously. This framework provides patterns to apply EIP-6963 for seamless connect flows, avoiding provider conflicts and ensuring correct wallet selection across desktop browsers.

What's the best way to handle wallet mobile deep linking and universal links?▼

The best way to handle mobile deep linking is to use universal links that route users directly to native wallet apps for signing. This framework covers deep linking patterns for both WalletConnect v2 fallbacks and direct mobile wallet integrations.

How does session persistence work for auto-reconnecting Ethereum wallets?▼

Session persistence for Ethereum wallets works by caching the connection state and provider information locally. This allows the dApp to auto-reconnect active sessions on page reloads, reducing redundant re-authentication prompts for returning users.

Can I use embedded wallets for new users with a WalletConnect v2 fallback?▼

Yes, you can use embedded smart wallets for new users alongside WalletConnect v2 fallbacks. This framework supports onboarding flows with embedded wallets and provides upgrade paths, while WalletConnect v2 handles external connections via QR codes and deep links.

Why does my dApp show inconsistent wallet connection states across providers?▼

Inconsistent wallet connection states occur because Ethereum dApp connections are fragmented across providers and devices. This framework offers cohesive UX patterns and error handling to resolve inconsistent states and standardize disconnect and reconnect flows.

Are there specific error handling patterns for ENS resolution during wallet connection?▼

Yes, there are specific error handling patterns for ENS resolution during wallet connection. This framework provides guidelines for ENS and name resolution alongside clear error states to ensure consumer-friendly messaging when resolution fails.