Can people spot a lookalike address?
Test whether people can confidently compare recipient details when an address looks similar to a saved or recent destination.
Product design case study · Crypto transfers
Making crypto transfers feel clearer and safer.
Sendsure explores how a wallet can help people review a recipient, catch network mismatches, understand fees, and make a more informed decision before sending crypto.
The product idea
Confidence before confirmation.
The most important moment in a crypto transfer may be the moment just before someone sends. Sendsure focuses on making that moment easier to understand.
Recipient review
Network check
Fee clarity
Review recipient
Check before you send
Recipient address
0x82a4...91c7
Network
Ethereum
Transfer amount
0.025 ETH
Send crypto
Where would you like to send?
Recipient
Saved contact
0x82a4...91c7
Asset
Ethereum · ETH
Amount
0.025 ETH
Project status: Sendsure is a self-initiated product
design project. This case study describes the problem, design direction,
and proposed validation approach. It does not claim a live wallet launch
or completed user-testing results.
01 · Context & opportunity
A small mistake can have a permanent consequence.
Sending crypto asks users to make several technical decisions. They may need to check a long wallet address, select the right network, understand transaction fees, and confirm an action that may not be reversible.
The problem
People are asked to verify details that are difficult to verify.
Long addresses are hard to scan. Similar-looking addresses can be confusing. Network choices and fees may feel unfamiliar. A standard confirmation screen can show the information without making the consequences easy to understand.
Design opportunity: Make important checks visible at the decision point, before the user commits to a transfer.
01
Address uncertainty
Long strings and lookalike addresses are difficult to compare by eye.
02
Network mismatch
Users may not understand whether the selected network matches the recipient's destination.
03
Unclear fees
Technical fee values can make it harder to understand the total cost before sending.
04
Finality of the action
A confirmation step should communicate what happens next and what may not be reversible.
02 · Research & problem validation
Turn possible risks into questions worth testing.
The design direction starts with plausible failure points in a crypto transfer. The next step is to validate which moments create the most confusion, hesitation, and preventable mistakes.
Do users understand network selection?
Check whether users can identify a network mismatch and explain why it matters before continuing.
Is the real cost clear?
Explore whether users understand the amount, fee, and estimated total when the cost is presented in familiar terms.
Research integrity: These are proposed research questions, not completed findings. No participant quotes, usability scores, or success metrics are claimed at this stage.
03 · Solution exploration
Move the important checks before the final tap.
Instead of relying on a generic confirmation screen, Sendsure introduces a clearer review journey. Each step is designed to help users understand what they are about to do.
Review the recipient
Give the destination a dedicated review step. Use readable address formatting and, where available, help users compare it with a trusted saved destination.
Check the network
Make the selected network explicit. If a mismatch is detected, explain the problem and block the default continuation path.
Explain the total cost
Present the transfer amount, network fee, and estimated total in a clear hierarchy, with a local-currency estimate where reliable conversion data is available.
Confirm and track
Explain that the transfer may not be reversible, then provide a clear status and receipt so users know what happened after they confirm.
04 · Core design decisions
Safety should be part of the flow, not an afterthought.
The design choices prioritize clarity, useful friction, and accessible feedback rather than adding warnings everywhere.
Make addresses easier to inspect
Use a monospace typeface and deliberate grouping to improve scanning. Similar-address comparison should only be presented when the product has reliable information to support it.
Block a detected mismatch by default
A mismatch should be explained in plain language, not shown as a color-only alert. Any expert override needs careful safety consideration and explicit confirmation.
Explain the cost in familiar terms
Keep the crypto amount, network fee, and estimated total distinct. Local-currency estimates should be labelled as estimates rather than guaranteed final costs.
Offer a small test send when appropriate
A test transfer can help in some situations, but it also has costs and limitations. Present it as an optional safeguard, not as a guarantee that a later transfer will be safe.
Make the consequence explicit
State clearly that crypto transfers may not be reversible. Use direct wording close to the final action rather than hiding the warning in general terms and conditions.
Never depend on color alone
Pair risk colors with labels, icons, and explanatory text. Support larger text, clear focus states, and an accessible alternative to press-and-hold confirmation.
05 · Interaction approach
From simply confirming to understanding the transfer.
The goal is not to add friction to every action. It is to place the right information where it can prevent confusion.
A generic confirmation
- Important details may be difficult to scan.
- Network choice may not be explained clearly.
- Fees can be separated from the amount the user cares about.
- A warning may not explain what the user should do next.
A guided review
- Recipient and network are reviewed before sending.
- Detected mismatches receive a clear explanation.
- Amount, fee, and estimated total are grouped together.
- The final action explains the consequence and next status.
Important: The comparison describes the intended design direction. It is not a claim that the experience has already outperformed an existing wallet in usability testing.
06 · Interface design
Designing the moments that matter.
The core journey moves from entering a transfer to checking the recipient, reviewing the network and cost, confirming the action, and understanding the final status.
01 — 06 / CORE FLOW
Begin with a clear next step.
Make the transfer action and required information easy to understand before the user starts.
Make the destination easy to review.
Keep the recipient information visible and provide a clear way to correct an entry before moving on.
Give the address a dedicated check.
Help users inspect the destination rather than asking them to accept a long string without context.
Make a mismatch understandable.
State the selected network clearly and explain what a detected mismatch means for the transfer.
Bring the cost together.
Present the amount, fee, and estimated total in one place before the user confirms.
Keep users informed afterwards.
Show a clear transfer state and preserve the receipt or transaction reference for later review.
Asset note: The carousel is wired up and responsive. The image paths above are descriptive placeholders, not verified filenames from your ZIP. Match each path to the corresponding supplied SVG before publishing.
07 · Edge cases & system states
A safer flow also needs to handle what goes wrong.
Error states are part of the product experience. They should explain the issue, give users a useful next step, and avoid suggesting that a risky action is safe.
Network mismatch
Clearly identify the selected network and the detected incompatibility. Block the normal path forward until the issue is resolved, where the product can reliably detect it.
Address needs attention
Explain what appears unusual and ask the user to verify the destination. Do not label an address safe unless the system has reliable evidence for that claim.
Fee estimate changes
Refresh the estimate when possible and explain that network fees can change. Keep the latest amount visible before the final confirmation.
Pending or failed transfer
Distinguish pending, confirmed, and failed states. Provide a transaction reference when available and avoid implying that a pending transfer has already completed.
08 · Validation plan
Test whether the design actually helps.
A proposed usability study compares a standard wallet-style flow with the Sendsure review journey. The aim is to find out whether clearer checks help people spot problems and understand their transfer before confirmation.
01 · Recruit a small participant group
Plan for around eight participants with a range of crypto familiarity. Treat the results as directional, not statistically representative.
02 · Run comparable tasks
Include a lookalike-address scenario and a network-mismatch scenario. Use safe prototype tasks only, not real transfers.
03 · Observe behavior
Record whether participants spot the issue, explain it in their own words, choose an appropriate next step, and understand the fee summary.
04 · Report the evidence honestly
Share the sample size, task outcomes, time taken, confusion points, and at least one design change made after testing. Do not publish success rates until the study is completed.
Current status: This is a proposed validation plan. Study results and measured usability outcomes have not been supplied, so no completion rates or improvement percentages are included.
09 · What this project explores
Good safety UX helps people understand, not just comply.
Sendsure is an exploration of how interaction design can make a technically complex and consequential action easier to reason about.
Clarity is a safety feature.
Address details, networks, fees, and consequences are not just supporting information. Their presentation can affect the decisions people make.
Warnings need useful next steps.
An alert is more helpful when it explains the issue and what to do next, rather than relying on red color or a generic error.
Validation is part of the design.
A safety-focused flow should be tested with realistic tasks. The final design needs evidence that people can understand and use it, not just a polished interface.
The takeaway
Designing confidence into high-stakes actions.
Sendsure explores a more considered crypto transfer experience: one that helps people review the destination, understand the network and cost, and know what happens after they confirm.