spesmilo / spesmilo/electrum

Small changes to initial setup, for new users trying to connect a hardware wallet.

Open
#9,296 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
8.6k
Forks
3.5k
Avg merge
2d 8h
Merged PRs (30d)
61

Description

This is by no mean a suggestion for an optimal flow, but something urgent has to be done. Even people who's been using bitcoin for years need their hand held at almost every step of initial setup.

image

People who have a hardware wallet are confused why they would need to CREATE a wallet as the first option?

On the next step they try Import Address, since they already have one.

image

The question asked is CREATE WALLET, Not "restore"

image The question suggest only two option "CREATE NEW or IMPORT SEED WORDS"

Most of the time the HWW won't be detected, But there are No mention of having to Connect and UNLOCK the device for it to be detected and in most case (Ledger) selecting the Bitcoin app

address type need an format example.
People get stuck there, not using the default option, worried to make a mistake.
Start with BC1...
Start with 1...
Start with 3...

After that, most people don't want mBTC, it's not a standard that's ever caught on but it's the default on Electrum, we're more likely to switch to hybrid sat-BTC interfaces. Would suggest defaulting to BTC or showing an option to select before loading the wallet.

Will try mocking up my UI suggestion in a further comment to this... If anything there should be a HARDWARE WALLET option at the step before, Shown before suggesting 2FA Multisig and Import xpub.

Or for now just say "

Create new / Restore wallet.

What kind of wallet do you want to create "or restore". And have as the 2nd option "Hardware wallets" that'd be jumping straight to Device detection.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by locating the initial setup screens and hardware-wallet detection flow, then review the wording and navigation for creating or restoring wallets. Done should be defined by a focused scope, such as a clear hardware-wallet path with device instructions, address examples, and an agreed currency default.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.