Onboarding people who are new to crypto

Someone new to crypto arriving at your product has to learn several unfamiliar ideas at once: wallets, networks, tokens, fees, signatures, and a recovery phrase that apparently can't be reset. Many onboarding flows try to explain all of it up front, in a carousel nobody reads, or none of it, leaving people to search for answers elsewhere.

There's a better middle path. Explain each idea at the moment it becomes relevant, in a sentence or two, and let people get value from the product before asking them to commit. This guide covers how to do that without scaring people or talking down to them.

Let people look before they commit

The first few minutes should show what the product does, not what it requires. A newcomer who sees live prices, a sample portfolio, or a swap quote for an amount they typed understands the point of the product. A newcomer who sees "Create a wallet" as the first screen has to trust you before they know what they're getting.

Practical ways to let people explore:

• Read-only browsing. Show markets, pools, collections and quotes without a wallet.
• Watch any address. Let people paste an address or ENS name to see a portfolio, so they can look at a public example.
• Typed-in amounts. Let the swap form calculate a quote for any amount, then ask for a wallet only when they press Swap.

When the moment to connect or create a wallet arrives, the person already has a reason.

Explain one idea at a time

Progressive disclosure means each concept appears where it's needed, not before. Map the moments in your flow to the idea each one requires:

Write each explanation once, put it in the interface at that moment, and link to a longer help article for anyone who wants depth. A short line inside the flow gets read far more often than a separate page.

Avoid analogies that mislead. "A wallet is like a bank account" sets the wrong expectations about recovery, support and reversibility. Describe what the thing does instead.

Talk about seed phrases without fear

The recovery phrase, usually 12 or 24 words, is the hardest part of self-custody to explain and the easiest to explain badly. Warnings full of skulls and red capital letters make people anxious without making them safer. Vague reassurance does the opposite. What helps is being specific and calm:

Your recovery phrase

These 12 words can restore your wallet on any device. Write them down on paper and keep them somewhere safe.

Anyone who has these words can take your funds. No legitimate app, website or support team will ever ask for them.

That's three facts: what it is, what to do, and what to watch out for. The last sentence is the most valuable part, because phishing attempts ask for exactly these words, and people who know nobody legitimate asks are much harder to trick.

A short check after setup, such as asking for two or three of the words in order, confirms the person saved them. Let them skip it and come back, rather than blocking them; then remind them gently, for example when their balance first goes above zero.

Some products create wallets behind an email login or passkey and don't show a recovery phrase at first. That can make the first session much easier, but it changes who controls recovery. If you take that route, say plainly how recovery works in your product, and how someone can move to a wallet they fully control later.

Pick sensible defaults

Every setting you show a newcomer is a decision they're not equipped to make yet. Choose defaults that are safe and correct for most people, and keep the controls one click away:

• Network. Pre-select the network your product works best on, and explain it only if they need to move funds there.
• Slippage. Use a modest default and hide the control under settings, with a plain label.
• Approvals. Request exact amounts by default, not unlimited approvals.
• Fees. Use the standard speed and show the cost in local currency.
• Hidden tokens. Hide unknown and airdropped tokens by default, so a newcomer's first look at their wallet isn't full of spam.

The first funds problem

A common place for newcomers to stall is getting funds into the right place. They bought crypto on an exchange, then discover it needs to be on a specific network, and that they also need a little of the network's own token to pay fees.

Design for this explicitly. On the receive screen, show the address with a QR code, the network name and logo, and a one-line warning to send only on that network. If the person has funds on a different network, say so and offer the next step. If they have tokens but no gas, tell them that before they try a transaction, not after it fails. Showing gas fees people understand covers how to word fee explanations.

Empty is the default state

For a newcomer, every screen starts empty: no balance, no activity, no history. Those empty screens are onboarding too. Each one should say what will appear there and offer the action that fills it, which empty states in wallets and dashboards works through in detail.

Test with real newcomers

Assumptions about what's obvious don't survive contact with someone who has never used a wallet. Sit with a few people who are new to crypto, give them a small amount to work with, and watch them complete one task. Note every pause and every question. Then fix the explanation at that exact point in the flow, using their words where you can. The same friction points come up repeatedly, as Web3 UX: where most dApps lose people describes, but your product will have its own.