Bitcoin Forum
April 21, 2026, 08:49:39 AM *
News: Latest Bitcoin Core release: 30.2 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Custom Derivation Path for Bip39 Restore  (Read 58 times)
cyberpass2 (OP)
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
November 06, 2025, 11:59:33 PM
 #1

Hello,

I have a custom derivation path, but I can't seem figure out what format I should use in Electrum when i restore my BIP39 seed:

I have keys with the following path:

m/84'/1'/0'/0/0'

I've tried the following custom derivation in Electrum:

m/84h/1h/0h/0/0h

I am able to derive them in Ian Coleman's script. Im not worried I lost my funds or anything but I'd be more comfortable knowing I can sweep the transactions using Electrum.

Charles-Tim
Legendary
*
Offline Offline

Activity: 2254
Merit: 6317


Leading Crypto Sports Betting & Casino Platform


View Profile
November 07, 2025, 12:04:46 AM
 #2

After you input your BIP39 seed phrase on Elecrum and you checked ✔️ BIP39, click on native segwit (p2wpkh).

..Stake.com..   ▄████████████████████████████████████▄
   ██ ▄▄▄▄▄▄▄▄▄▄            ▄▄▄▄▄▄▄▄▄▄ ██  ▄████▄
   ██ ▀▀▀▀▀▀▀▀▀▀ ██████████ ▀▀▀▀▀▀▀▀▀▀ ██  ██████
   ██ ██████████ ██      ██ ██████████ ██   ▀██▀
   ██ ██      ██ ██████  ██ ██      ██ ██    ██
   ██ ██████  ██ █████  ███ ██████  ██ ████▄ ██
   ██ █████  ███ ████  ████ █████  ███ ████████
   ██ ████  ████ ██████████ ████  ████ ████▀
   ██ ██████████ ▄▄▄▄▄▄▄▄▄▄ ██████████ ██
   ██            ▀▀▀▀▀▀▀▀▀▀            ██ 
   ▀█████████▀ ▄████████████▄ ▀█████████▀
  ▄▄▄▄▄▄▄▄▄▄▄▄███  ██  ██  ███▄▄▄▄▄▄▄▄▄▄▄▄
 ██████████████████████████████████████████
▄▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▄
█  ▄▀▄             █▀▀█▀▄▄
█  █▀█             █  ▐  ▐▌
█       ▄██▄       █  ▌  █
█     ▄██████▄     █  ▌ ▐▌
█    ██████████    █ ▐  █
█   ▐██████████▌   █ ▐ ▐▌
█    ▀▀██████▀▀    █ ▌ █
█     ▄▄▄██▄▄▄     █ ▌▐▌
█                  █▐ █
█                  █▐▐▌
█                  █▐█
▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▀█
▄▄█████████▄▄
▄██▀▀▀▀█████▀▀▀▀██▄
▄█▀       ▐█▌       ▀█▄
██         ▐█▌         ██
████▄     ▄█████▄     ▄████
████████▄███████████▄████████
███▀    █████████████    ▀███
██       ███████████       ██
▀█▄       █████████       ▄█▀
▀█▄    ▄██▀▀▀▀▀▀▀██▄  ▄▄▄█▀
▀███████         ███████▀
▀█████▄       ▄█████▀
▀▀▀███▄▄▄███▀▀▀
..PLAY NOW..
cyberpass2 (OP)
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
November 07, 2025, 12:10:04 AM
 #3

Yes. I did that, but I want to derive hardened addresses.
pooya87
Legendary
*
Offline Offline

Activity: 4102
Merit: 12279



View Profile
November 07, 2025, 03:36:42 AM
Merited by hosemary (2), Charles-Tim (2)
 #4

Electrum doesn't support hardened addresses, probably because of the way the wallet is designed (needs to be able to derive addresses from master public key).

So when you enter any derivation path, it considers it as the root and then automatically derives you keys at m/0/ and m/1/  (m/0/0, m/0/1, m/0/2, ... are main addresses, m/1/0, m/1/1, m/1/2, ... are change addresses). That way you can easily get the master public key of this wallet and then create a watch only wallet from it without needing the seed itself.

███████████████████████████
███████▄████████████▄██████
████████▄████████▄████████
███▀█████▀▄███▄▀█████▀███
█████▀█▀▄██▀▀▀██▄▀█▀█████
███████▄███████████▄███████
███████████████████████████
███████▀███████████▀███████
████▄██▄▀██▄▄▄██▀▄██▄████
████▄████▄▀███▀▄████▄████
██▄███▀▀█▀██████▀█▀███▄███
██▀█▀████████████████▀█▀███
███████████████████████████
.
.Duelbits PREDICT..
█████████████████████████
█████████████████████████
███████████▀▀░░░░▀▀██████
██████████░░▄████▄░░████
█████████░░████████░░████
█████████░░████████░░████
█████████▄▀██████▀▄████
████████▀▀░░░▀▀▀▀░░▄█████
██████▀░░░░██▄▄▄▄████████
████▀░░░░▄███████████████
█████▄▄█████████████████
█████████████████████████
█████████████████████████
.
.WHERE EVERYTHING IS A MARKET..
█████
██
██







██
██
██████
Will Bitcoin hit $200,000
before January 1st 2027?

    No @1.15         Yes @6.00    
█████
██
██







██
██
██████

  CHECK MORE > 
nc50lc
Legendary
*
Offline Offline

Activity: 3122
Merit: 8655


Self-proclaimed Genius


View Profile
November 07, 2025, 05:35:41 AM
Merited by Charles-Tim (1)
 #5

Yes. I did that, but I want to derive hardened addresses.
Your option is limited since you've used a custom non-standard derivation path.

Not in Electrum or even Sparrow, but you can import the master private key to Bitcoin Core via "descriptor". (equivalent to BIP39 tool's "BIP32 Root Key")
Import it like this (preferably to a blank wallet):
Code:
importdescriptors "[{\"desc\": \"wpkh(your_xprv_key/84h/1h/0h/0/*h))#00000000\",\"timestamp\": \"0\",\"watching-only\": false,\"active\": true,\"internal\": false,\"range\": [0,999]}
You should replace the checksum "#00000000" with one that'll be displayed in the error message about checksum mismatch or use getdescriptorinfo first.
To import the change addresses, import another with "internal: true" flag and chain_index (External/Internal) derivation path switched to from "0' to "1".

███████████████████████████
███████▄████████████▄██████
████████▄████████▄████████
███▀█████▀▄███▄▀█████▀███
█████▀█▀▄██▀▀▀██▄▀█▀█████
███████▄███████████▄███████
███████████████████████████
███████▀███████████▀███████
████▄██▄▀██▄▄▄██▀▄██▄████
████▄████▄▀███▀▄████▄████
██▄███▀▀█▀██████▀█▀███▄███
██▀█▀████████████████▀█▀███
███████████████████████████
.
.Duelbits PREDICT..
█████████████████████████
█████████████████████████
███████████▀▀░░░░▀▀██████
██████████░░▄████▄░░████
█████████░░████████░░████
█████████░░████████░░████
█████████▄▀██████▀▄████
████████▀▀░░░▀▀▀▀░░▄█████
██████▀░░░░██▄▄▄▄████████
████▀░░░░▄███████████████
█████▄▄█████████████████
█████████████████████████
█████████████████████████
.
.WHERE EVERYTHING IS A MARKET..
█████
██
██







██
██
██████
Will Bitcoin hit $200,000
before January 1st 2027?

    No @1.15         Yes @6.00    
█████
██
██







██
██
██████

  CHECK MORE > 
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!