<p>Instead of using <code>bip32 or bip44</code> paths what if I use a custom derivation path,<br>
For example:  <code>m/0/0/55/1/1/0</code></p>

<p>I am thinking even if the private key is exposed then can someone guess the derivation path ?</p>

CC BY-SA 4.0
2018-06-07T12:41:03.870Z
If the private key for an address is exposed you don't need to guess the derivation path
Raghav Sood
CC BY-SA 4.0
2018-06-07T12:43:22.657Z
Ie the above paths private key is exposed and using that private key anyone can get the other private keys ie  address 0,1,2,3
f4r4
CC BY-SA 4.0
2018-06-07T12:45:12.710Z
So are there any advantages in having custom derivation paths ?
f4r4
CC BY-SA 4.0
2018-06-07T13:37:30.470Z
Some projects use them to specify derivation schemes not covered by BIP44. Otherwise, not really. The whole point of the path is to create a standard, reproducible flow.
Raghav Sood
<bip32-hd-wallets><bip44>
Custom derivation path
f4r4
# Custom derivation path

(Asked by: username_0 on 2018-06-07)

Instead of using `bip32 or bip44` paths what if I use a custom derivation path,  
For example: `m/0/0/55/1/1/0`

I am thinking even if the private key is exposed then can someone guess the derivation path ?

**Tags:** bip32-hd-wallets, bip44

> **Comments:**
> **username_1**: If the private key for an address is exposed you don't need to guess the derivation path  
> **username_0**: Ie the above paths private key is exposed and using that private key anyone can get the other private keys ie  address 0,1,2,3  
> **username_0**: So are there any advantages in having custom derivation paths ?  
> **username_1**: Some projects use them to specify derivation schemes not covered by BIP44. Otherwise, not really. The whole point of the path is to create a standard, reproducible flow.  

---

## 0 answers

