You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Don't know what exactly happen, but I had hided the second account.
few weeks later upgraded bitcoin app on the key.
few weeks later when I opened the BTC app again I'm unable to get back the second account.
I tried to re-create a second account, it appears but it's empty
I noticed when I delete the newly created second account that the root bip44 path is 49'/0'/2'.
I was believing index were 0 based and first address of first account must be 49'/0'/0'/0'
and first address of second account must be 49'/0'/1'/0' vs 49'/0'/2'/0'
Do I miss something, and do you have a working fix to get back access to funds of my second account ?
thanks.
EDIT
furthermore if I check device logs I saw HTTP GET Requests to
Hi, I had setup my nano S ledger with the 24 words.
I send BTC to the main account segwit (4 times) and decided to create a second one account.
I send funds to the second one : https://blockchain.info/address/34X15ArQpQz2MGXrS8b2V4fJVhko4aSgGn.
Don't know what exactly happen, but I had hided the second account.
few weeks later upgraded bitcoin app on the key.
few weeks later when I opened the BTC app again I'm unable to get back the second account.
I tried to re-create a second account, it appears but it's empty
I noticed when I delete the newly created second account that the root bip44 path is 49'/0'/2'.
I was believing index were 0 based and first address of first account must be 49'/0'/0'/0'
and first address of second account must be 49'/0'/1'/0' vs 49'/0'/2'/0'
Do I miss something, and do you have a working fix to get back access to funds of my second account ?
thanks.
EDIT
furthermore if I check device logs I saw HTTP GET Requests to
Mon, 29 Jan 2018 05:12:38 GMT,INFO,WalletLayoutRecoveryTask,Recover batch 0 for account 1
https://api.ledgerwallet.com/blockchain/v2/btc/addresses/34X15ArQpQz2MGXrS8b2V4fJVhko4aSgGn[...truncated...]
which tends to prove that it's my generated public address for second account, and you could check your servers logs you will see a hit
The text was updated successfully, but these errors were encountered: