To onboard people who are new to crypto, let them use the product before you ask for a wallet, and ask only when they try something that needs one. Say what connecting unlocks before the picker opens, give people with no wallet a way forward, and explain every signature in plain words before the wallet shows it. Then design the wrong-network, no-gas, pending and failed states as carefully as success.
Why do people new to crypto give up at the wallet step?
Most people who own crypto rarely use it. a16z’s State of Crypto Report 2024 estimated 30 to 60 million monthly active crypto users, 5 to 10% of the 617 million people who own crypto. Trust starts low too: in a 2024 Pew Research Center survey, 63% of US adults said they had little or no confidence that current ways to invest in, trade or use cryptocurrency are reliable and safe. The person at your wallet step is often new or out of practice, and half expects a trick.
What they complain about is concrete. In our crypto trust research we read 1,925 passages about wallets, staking and failed transactions, and 384 were about trusting or using a crypto product. Common complaints were failed or stuck transactions (80, and 53 of those came from people it happened to), connecting, signing and approvals (70), and products too complex for a first-time user (70). In a second set, about token rewards and airdrops, 23 of 208 passages said connecting a wallet or signing is the risky part.
The fear is reasonable. Scam Sniffer counted $83.85 million taken by wallet-drainer phishing in 2025, from 106,106 victims. That is down 83% from 2024’s $494 million, but the report says new drainers keep replacing the ones that quit. The biggest theft of 2025, $6.5 million in September, was a permit signature. Across the 11 thefts of $1 million or more, Permit and Permit2 signatures accounted for 38% of the losses. A permit is a signature, not a transaction, so it can look like a harmless message. People who can’t tell a sign-in from a permission either refuse to sign anything or sign everything. Your interface has to tell them which one is coming.
Rough guide. Eight of the practices in this guide; the bands are our judgment, not measured thresholds.
Embed this chart
Free to use with the credit line. Paste this into your page:
How do 42 live DeFi apps handle people without a wallet?
Most assume you already have one. On October 31, 2026 we opened 42 live DeFi apps with no wallet installed, twice and an hour apart, and clicked their connect button. In the 28 where a list of wallets appeared:
- 18 offered no worded path for someone without a wallet, such as “get a wallet” or “create one”.
- 23 didn’t say in words what a wallet is. All 5 that did were a wallet library’s standard picker, and 8 of the others offered help only as a “?” icon.
- 26 offered no email or social sign-in.
- 2 made people tick a terms box before they could choose a wallet.
- 5 offered no WalletConnect option or QR code for a phone wallet.
The basics were mostly in place: none opened a wallet picker before a click, and 39 of 41 connect buttons had a name a screen reader can announce.
How we picked and measured: the apps come from the 500 largest in CoinGecko’s decentralized-finance category. We left out exchanges, bridges, chains and infrastructure, 95 apps whose terms bar automated visits, 129 whose terms we couldn’t find and 6 that were closed to our US connection, so the set leans toward smaller apps (43 of the 53 we tried ranked 101 to 500). We clicked only the connect button and never accepted terms. A value counts only where both visits agreed, and a second reviewer, an AI model, checked every wallet list against its screenshots. No app is named. App selection data is powered by CoinGecko, and the aggregate counts are a CSV download.
What should people see before you ask for a wallet?
The product. Apple’s Human Interface Guidelines say people should ideally understand an app simply by using it, and that a permission request belongs at the moment someone first reaches the feature that needs it. Android’s guidance on permissions says the same: ask in context, explain why before the system dialog appears, and don’t block someone who says no. A wallet connection is a permission, so treat it like one.
- Let people browse without connecting: prices, pools, the token page, the docs and anything else that’s public.
- Ask for a wallet when someone tries something that needs one: staking, claiming, buying, voting or saving.
- On the screen before the picker, say what connecting unlocks and what it doesn’t do. For example: “Connect to see your balance and stake. Connecting doesn’t move funds or cost anything.”
- Give every step a way back. Someone who isn’t ready to connect should land somewhere useful, not on an empty page.
In the staking product we designed for HubsAI, an empty dashboard said what connecting unlocks, and the welcome step warned that a signature request was coming before the wallet opened. The HubsAI case study shows the connect flow step by step.
How do you onboard someone who doesn’t have a wallet?
Give the wallet picker three exits that aren’t dead ends.
- Create one here. Some stacks let people create a wallet inside your product with an email or a passkey and connect a self-custody wallet later. Say in plain words who holds the keys and how to move the funds out.
- Get one and come back. Recommend one or two wallets that work with your chain, link to their official sites, and bring people back to the step they left.
- Keep going without one. Let people finish browsing, save what they were looking at, or leave an email, and ask for the wallet when they return.
Smart accounts can make the first step lighter. The ERC-4337 standard for account abstraction lets developers pay fees for their users and bundle several operations into one, so a first action doesn’t have to start with buying a gas token. If you sponsor fees, say so on the screen.
On Everreach Labs’ $EVER claim portal, which we designed, onboarding had an “I don’t have a wallet” path, so a player without crypto was never stuck at the picker.
How do you explain signatures and approvals?
Explain each request in your own interface before the wallet shows it. A wallet pop-up shows what the contract asks for, which is rarely written for people. EIP-712 was written because signed messages appeared to users as an opaque hex string with little context; typed data lets a wallet show named fields instead. Use it, and give the fields names a person can read.
| Request | What it does | Say this before the wallet opens |
|---|---|---|
| Sign-in message (Sign-In with Ethereum) | Proves the person controls the address. It’s checked off-chain, so nothing is sent to the chain and there’s no fee | “Sign in with your wallet. It’s a free message: it doesn’t move funds or start a transaction.” |
| Transaction | Sent to the chain. It can move tokens, and it costs a network fee | What will happen, the amount, the fee in dollars and roughly how long it takes |
| Token approval | Lets a contract spend up to a set amount of one token | The token, the amount this action needs and how to remove the permission later |
| Permit signature (ERC-2612) | Grants the same spending permission as an approval, as a signature with no transaction | The same as an approval. It’s a signature, so it can look like a free message |
Ask approvals for the amount the action needs, and show that amount on the screen. An unlimited approval saves a step later, but careful users check approval amounts, and a new user has no way to judge whether it’s safe.
How should you handle the wrong network, gas and slow transactions?
These states decide whether a new user’s first action succeeds. Give each one its own screen.
- Wrong network. Detect it before the person acts, say which network the product runs on, and offer a button that asks their wallet to switch. A page of zeros on the wrong network looks like lost money.
- No gas token. Say which token pays the fee on this network, roughly how much is enough and where to get it, or sponsor the fee and say so.
- Pending. Say the transaction is waiting on the network, link it on the block explorer, and keep it visible if the person leaves the page.
- Failed. Say what failed, whether any funds moved, whether the fee was spent and what to do next. Failed or stuck transactions came up often in our wallets set, at 80 of 384 passages.
- Empty. No balance, nothing staked, no history yet: each gets a screen that says what to do first, not a row of zeros.
- Claim outcomes. If the product pays out tokens, a wallet that isn’t eligible, a claim already made, a window that hasn’t opened or has closed, and a claim that is rejected each need their own screen. They are set out, with sources, in our token launch website checklist.
For HubsAI’s $HUBS launch we mapped 32 states, 9 of them errors or empty states, before designing a single screen, and its notifications said plainly when a stake failed or the network was congested.
What should the first success look like?
Confirm it in your product, not only in the wallet: what happened, the new balance or position, a link to the transaction and the one next step. Then teach the next feature when someone reaches it. Apple’s guidelines suggest context-specific tips instead of a single onboarding flow, because people learn better when they can concentrate on one task before meeting new information. Put a one-line explanation next to the button that needs it, rather than a tour of terms before the first click.
How do you test wallet onboarding?
- Recruit people who have never used a wallet, and test on a phone.
- Run five setups: no wallet, a fresh wallet with no funds, a wallet on the wrong network, a small balance, and a transaction you make fail on a testnet.
- Before each wallet pop-up, ask what they think it will do. Every wrong guess is a line your interface should have said first.
- Write down where each person stops, and fix those screens before adding features.
How does Alterra Studio help with wallet onboarding?
We design wallet onboarding as part of the product: what people see before they connect, the path for people with no wallet, a plain-words explanation for every signature, and the network, gas, pending, failed and empty states. For HubsAI’s $HUBS launch we designed a staking product of 50 screens and states, from wallet connect to claiming rewards. For Everreach Labs, which kept us as its design team through 2024 and 2025, the $EVER claim portal had a path for players without a wallet. See our product design service and how we work with Web3 teams.
The short version
- Show the product first, and ask for a wallet only when someone tries something that needs one.
- Say what connecting unlocks before the picker opens, and give people with no wallet a way forward. In our October 2026 check, 18 of 28 live DeFi wallet pickers had no worded path for them.
- Explain every signature in your own interface before the wallet opens: sign-in message, transaction, approval or permit.
- Design the wrong-network, no-gas, pending, failed and empty states, and say whether funds moved.
- Test on a phone with people who have never used a wallet, and fix the screens where they stop.
Sources
Checked October 30, 2026.
- a16z, State of Crypto Report 2024 (Daren Matsuoka, Robert Hackett and Eddy Lazzarin, October 16, 2024), monthly active users and owners.
- Pew Research Center, On cryptocurrency, 63% of US adults not confident it’s safe, reliable (October 24, 2024).
- Scam Sniffer, Scam Sniffer 2025: Crypto Phishing Losses Fall 83% to $84 Million (January 3, 2026), losses, victims and signature types in thefts of $1 million or more, with 2024 for comparison.
- Ethereum Improvement Proposals: ERC-4361: Sign-In with Ethereum, EIP-712: Typed structured data hashing and signing, ERC-2612: Permit Extension for EIP-20 Signed Approvals and ERC-4337: Account Abstraction Using Alt Mempool.
- Apple, Human Interface Guidelines: Onboarding.
- Android Developers, Request runtime permissions.
- Alterra Studio, wallet-connect check of 42 DeFi apps (October 31, 2026), aggregate counts as a CSV download. App selection from CoinGecko’s decentralized-finance category, powered by CoinGecko.
- Alterra Studio, Why people don’t trust crypto products: 978 comments, sorted (October 2026), with the aggregate counts as a CSV download.
Frequently asked questions
What are the best practices for wallet onboarding UX?
Let people use the product before you ask for a wallet, and ask only when they try something that needs one. Say what connecting unlocks before the wallet picker opens, give people without a wallet a way forward, explain each signature in your own interface before the wallet shows it, and design the wrong-network, no-gas, pending and failed states as carefully as success. Test it on a phone with someone who has never used a wallet.
How do you onboard users who don't have a crypto wallet?
Give the wallet picker exits that aren't dead ends: create a wallet inside your product with an email or a passkey where your stack supports it, get a recommended wallet and come back to the same step, or keep browsing and connect later. Everreach Labs' $EVER claim portal, which we designed, had an "I don't have a wallet" path, so a player without crypto was never stuck at the picker.
What's the difference between signing a message and sending a transaction?
A sign-in message proves you control an address. It's checked off-chain, so nothing is sent to the chain and there's no fee. A transaction is sent to the chain, can move tokens and costs a network fee. A token approval lets a contract spend your tokens, and a permit signature grants the same right without a transaction, which is why your interface should say which one is coming before the wallet opens.
Should a dApp make people connect a wallet first?
Not to look around. Apple's onboarding guidelines say people should ideally understand an app by using it, and that a permission request belongs at the moment someone first reaches the feature that needs it. Treat the wallet the same way: show the product, the terms and the numbers first, and ask for a connection when someone tries to stake, claim, buy or save something.
How should a dApp handle the wrong network or a missing gas token?
Detect both before the person acts. For the wrong network, say which network the product runs on and offer a button that asks the wallet to switch. For a missing gas token, say which token pays the fee, roughly how much is enough and where to get it, or sponsor the fee and say so on the screen.
Want a straight answer for your company? Book a 30-minute call. We'll look at your situation and tell you what we'd do, even if we're not the right fit. Book a 30-minute call →