<p>Right. PIN just protect the configuration. It is not an input in the calculation.</p>

<ol>
<li>The first normal address should be m/44'/0'/0'/0/0, the first *change address should be m/44'/0'/0'/1/0.</li>
</ol>

<p>If you use segwit-p2sh m/49'/0'/0'/0/0 and m/49'/0'/0'/1/0. Native segwit: m/84'/0'/0'/0/0 and m/84'/0'/0'/1/0. And so on</p>

<ol start="4">
<li>Use the command line utils in pycoin. Pretty up-to-date. You have to somehow start from the seed though. They don't support BIP39.</li>
</ol>

<p>EDIT: The Master Public given by ledger wallet is already derived so: to obtain the first 10 addresses with ku (pycoin) this work for me (segwit):</p>

<p><code>
ku -j -s0/0-9 xpubYourMasterPublicKeyHere |jq '.p2sh_segwit'
</code></p>

<p>If you don't use segwit it's much easier:</p>

<p><code>
ku -s0/0-9 -a xpubYourMasterPublicKeyHere
</code></p>

<p>DISCLAIMER: Don't send money on a derivation you have obtained like this unless you know exactly what you're doing!</p>

<p>Check that the addresses produced are the same AND you have to use the address try first with a small amount to test and check the landing on Ledgerwallet.</p>

CC BY-SA 3.0
2018-03-20T16:05:04.963Z
maybe the master public you have used is already derived to m/44/0'/0' so you have to add only "0/0", "0/1", etc. If you have taken the master public from Ledger wallet you are in this situation.
Gabriele Domenichini
CC BY-SA 3.0
2018-03-10T22:29:26.210Z
m/44'/0'/0'/0/0 did not generate any of the above addresses that I have from my ledger.
Patoshi パトシ
CC BY-SA 3.0
2018-03-09T07:37:34.187Z
2018-03-20T16:02:15.573Z
2018-03-20T16:02:15.573Z
Gabriele Domenichini
<p>I have the following example seed:</p>

<blockquote>
  <p>morning twist board pelican denial retire middle inherit evil
  ritual omit fade general toddler grace evoke recipe
  sad minor destroy public dawn scissors cube</p>
</blockquote>

<p>I'm trying to generate the same addresses on the ledger site which is showing up on my device: <a href="https://www.ledgerwallet.com/support/bip39-standalone.html" rel="nofollow noreferrer">https://www.ledgerwallet.com/support/bip39-standalone.html</a></p>

<p>My intial pin was 5555 and my first bitcoin address is: 12mCn27...</p>

<p>I also set a "passphrase" of just the letter "a" which generates btc address: 1NSXBid...</p>

<p>I then did an attach to pin with the pin: 4555 which generates btc: 17Dn62...</p>

<p>I then added a passphrase to the 4555 pin with just the letter "b" and I get the following btc address: 1HBPpj...</p>

<ul>
<li>When setting up ledger nano s initially is the address randomized? And what deviration path does it start from?</li>
<li>I tried pasting the example seed into <a href="https://www.ledgerwallet.com/support/bip39-standalone.html" rel="nofollow noreferrer">https://www.ledgerwallet.com/support/bip39-standalone.html</a> and I can't find the initial pin 5555 setup of address: 12mCn27</li>
<li><p>If I'm able to set different pins, where do I type this pin on the Mnemonic Code Converter page? It's not the passphrase field thats for sure.</p></li>
<li><p>If I wanted to recover all those private keys with the above scenarios with different pins  and passphrases. How can I?</p></li>
</ul>

CC BY-SA 3.0
2018-03-08T18:41:05.370Z
It looks like the PIN doesnt matter. The passphrase "b" I used with 4555 pin also generates the same exact address if my pin is 5555 with passphrase "b" aswell. Looks like the PIN is used only to physically access the device itself and doesn't communicate at all with the connected computer or it being used for address generation.
Patoshi パトシ
CC BY-SA 3.0
2018-03-11T04:30:03.217Z
I also just tried restoring this seed on another ledger and I'm getting a totally different bitcoin address. why is that?
Patoshi パトシ
<wallet-recovery><seed><ledger-hardware-wallet><recover-private-key><mnemonic-seed>
Manually extracting ledger nano s wallet public / private keys using "Mnemonic Code Converter" from ledger
Patoshi パトシ
# Manually extracting ledger nano s wallet public / private keys using "Mnemonic Code Converter" from ledger

(Asked by: username_0 on 2018-03-08)

I have the following example seed:

> morning twist board pelican denial retire middle inherit evil
> ritual omit fade general toddler grace evoke recipe
> sad minor destroy public dawn scissors cube

I'm trying to generate the same addresses on the ledger site which is showing up on my device: <https://www.ledgerwallet.com/support/bip39-standalone.html>

My intial pin was 5555 and my first bitcoin address is: 12mCn27...

I also set a "passphrase" of just the letter "a" which generates btc address: 1NSXBid...

I then did an attach to pin with the pin: 4555 which generates btc: 17Dn62...

I then added a passphrase to the 4555 pin with just the letter "b" and I get the following btc address: 1HBPpj...

* When setting up ledger nano s initially is the address randomized? And what deviration path does it start from?
* I tried pasting the example seed into <https://www.ledgerwallet.com/support/bip39-standalone.html> and I can't find the initial pin 5555 setup of address: 12mCn27
* If I'm able to set different pins, where do I type this pin on the Mnemonic Code Converter page? It's not the passphrase field thats for sure.
* If I wanted to recover all those private keys with the above scenarios with different pins and passphrases. How can I?

**Tags:** wallet-recovery, seed, ledger-hardware-wallet, recover-private-key, mnemonic-seed

> **Comments:**
> **username_0**: It looks like the PIN doesnt matter. The passphrase "b" I used with 4555 pin also generates the same exact address if my pin is 5555 with passphrase "b" aswell. Looks like the PIN is used only to physically access the device itself and doesn't communicate at all with the connected computer or it being used for address generation.  
> **username_0**: I also just tried restoring this seed on another ledger and I'm getting a totally different bitcoin address. why is that?  

---

## 1 answers

### Answer by username_1 on 2018-03-09. Score: 1 | Accepted answer

Right. PIN just protect the configuration. It is not an input in the calculation.

1. The first normal address should be m/44'/0'/0'/0/0, the first \*change address should be m/44'/0'/0'/1/0.

If you use segwit-p2sh m/49'/0'/0'/0/0 and m/49'/0'/0'/1/0. Native segwit: m/84'/0'/0'/0/0 and m/84'/0'/0'/1/0. And so on

4. Use the command line utils in pycoin. Pretty up-to-date. You have to somehow start from the seed though. They don't support BIP39.

EDIT: The Master Public given by ledger wallet is already derived so: to obtain the first 10 addresses with ku (pycoin) this work for me (segwit):

`ku -j -s0/0-9 xpubYourMasterPublicKeyHere |jq '.p2sh_segwit'`

If you don't use segwit it's much easier:

`ku -s0/0-9 -a xpubYourMasterPublicKeyHere`

DISCLAIMER: Don't send money on a derivation you have obtained like this unless you know exactly what you're doing!

Check that the addresses produced are the same AND you have to use the address try first with a small amount to test and check the landing on Ledgerwallet.

> **Comments:**
> **username_0**: m/44'/0'/0'/0/0 did not generate any of the above addresses that I have from my ledger.  
> **username_1**: maybe the master public you have used is already derived to m/44/0'/0' so you have to add only "0/0", "0/1", etc. If you have taken the master public from Ledger wallet you are in this situation.  

---

