Tezos CLI，Ledger Nano，Tezbox和HD Wallet：访问我的xtz时出现问题

Question

Tezos CLI，Ledger Nano，Tezbox和HD Wallet：访问我的xtz时出现问题

- 6
- 258 2019-04-14
我阅读了Ledgernano S文档的一部分(包括HD Wallet和BIP39/BIP44派生路径以及BOLOS系统),您可以在 https://ledger.readthedocs.io/en/latest/background/introduction.html ). 我还查看了不同的来源,以更好地理解我可能犯的错误,或者可以重用一些代码来编写更好的脚本来测试值并找到我的PKH: https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki#use-cases https://iancoleman.io/bip39/ 直到现在,我还没有发现比暴力破解更好的功能(分类帐提供的安全性确实迫使该解决方案生效,这是可以的).

一开始,我跳到了第一个tezbox版本,该版本允许与我的Ledger Nano S链接. 在某个时候,我同时删除了chrome导航器和钱包中的数据.从那时起,我一直在尝试访问我的xtz.我知道tz1 PKH,也有我的Ledger Nano S.

我强行将路径44'/1729'/0'/0'强制修改为"派生路径"中的倒数第二个值,但没有成功.

所以我的问题是:

tezos-client的先前版本中是否有更改会影响新PKH(HD Wallet的派生树)的创建,是否会干扰我使用tezos CLI蛮力尝试的尝试?

针对tezbox团队的问题:您是否进行了更改,发布的第一个版本中是否存在一个错误,该错误会影响PKH的派生并阻止我生成我的PKH,而我的资金已锁定在当前版本的tezbox上?例如,是否有可能修改PATH,包括后来修改的44'/1729'?

我想非常清楚地表明,我不想怪任何人(只有我),而只是拥有对我的调查至关重要的信息,以便再次访问我的xtz令牌.

非常感谢您的回答！
I read a part of Ledger nano S documentation (including HD Wallet and BIP39/BIP44 derivation path, and BOLOS system, that you can find at https://ledger.readthedocs.io/en/latest/background/introduction.html). I also looked at different sources, either to better understand an error I could have made, or some code I could reuse to make a better script to test the values and find my PKH: https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki#use-cases https://iancoleman.io/bip39/ I did not find better than bruteforcing until now (the security the ledger is offering does force that only solution, which is ok).

In the beginning, I jumped on the first tezbox version that allowed linking with my Ledger Nano S. At some point I deleted the data in the chrome navigator and the wallet at the same time. I have tried since then to get access to my xtz. I know the tz1 PKH and I have my Ledger Nano S.

I brute-forced the path, 44'/1729'/0'/0' modifying incrementally the 2 last value in the Derivation Path, without success.

So my questions are:

Was there a change in previous version of the tezos-client that could affect the creation of new PKH (the derivation tree for HD Wallet), that would disrupt my attempts to brute-force my way using tezos CLI?

Question addressed to tezbox team: did you change something, was there a bug in the first versions published which could affect the derivation of PKH and preventing me to generate my PKH where my funds are locked on the current version of tezbox? Was there a possibility, for example, to modify the PATH, including 44'/1729', corrected afterwards?

I want to make very clear that I don't want to blame anyone else (but me), but merely have information that would be crucial to my investigation to access my xtz tokens again.

Thanks a lot in advance for your answers!
ledger tezos-client tezbox
- 原文
- tndnz

- 嗨,欢迎来到tezos堆栈交流！请提供您所指文档的链接.它将有助于更好地了解,谢谢！
  
  hi, welcome to tezos stack exchange! please provide link of the docs you are referring to. It will help understand better, thanks!
  - 0
  - 2019-04-14
  - Ezy
- H,您说您尝试过蛮力推导路径的最后2个部分,但是您是否使用3≠曲线尝试了它们?
  
  H, you say you tried to brute force the last 2 parts of the derivation path, but did you try them with the 3 ≠ curves?
  - 0
  - 2019-04-14
  - Seb Mondet
- 嗨,Seb,我假设默认情况下使用ed25519曲线方案的tezbox和tezos应用程序.您是否认为可能是其他原因?-因为我没有更改此设置.我将对此进行检查,以检查是否可以在应用程序端进行更改.
  
  Hi Seb, I assumed tezbox and tezos application used by default the ed25519 curve scheme. Do you think it could be otherwise?--because I did not change this setup. I will look into that to check if it can have been changed on the application side.
  - 0
  - 2019-04-15
  - tndnz
- @Ezy,谢谢.顺便说一句,我想对以前不是我的帖子的编辑表示歉意,但是作为新用户,我无法回答或评论.实际上,这更多是急于寻求答案的结果,但并不是要绕过规则或污染讨论.抱歉
  
  @Ezy, thank you. BTW I wanted to apologize before for the editing of a post which was not mine, but as a new user I could not answer or comment. It was really more the result of rush to try to get an answer, but not intended to bypass rules or pollute discussions. Sorry for that.
  - 0
  - 2019-04-15
  - tndnz
- 最近,我无法通过TezBox访问我的Ledger NanoS.路径('44'/1729'/0'/0'`)似乎错误.我可以使用Galleon访问它,它使用不同的路径:'44'/1729'/0'/0'/0'`.不知道这是否特定于我的账本,但希望对您有所帮助.
  
  Recently I could not access my Ledger Nano S via TezBox. The path (`44'/1729'/0'/0'`) seems wrong. I could access it using Galleon, which uses a different path: `44'/1729'/0'/0'/0'`. Not sure if this is specific to my Ledger or not, but I hope it helps.
  - 0
  - 2019-04-18
  - palthk_on
- 您好@pathk_on,谢谢您的建议.当我最初通过tezbox链接分类帐时,并按照默认的PATH 44'/1729'/0'/0'进行链接,这并没有改变我的问题.您可以添加一个级别,但是应该通过Tezos CLI`tezos-clientimport secret key your_ledger" ledger://animals-animals-strange-incantation/ed25519/0'/0'/0'"找到相同的PKH,其中您添加此额外的"级别".不管怎么说,还是要谢谢你.
  
  Hello @pathk_on, thanks for the suggestion. It does not change my problem as I initially linked my ledger via tezbox, and by doing so following the 44'/1729'/0'/0' default PATH hierarchy. You can add a level, but you should find the same PKH through Tezos CLI `tezos-client import secret key your_ledger "ledger://animals-animals-strange-incantation/ed25519/0'/0'/0'"` where you add this extra 'level'. Thanks anyway.
  - 0
  - 2019-04-23
  - tndnz
- 你解决这个问题了吗我有同样的问题.允许时,我将旧地址迁移到分类帐中.现在我无法访问我的tezos.
  
  did you solve this problem. I have the same exact problem. I migrated my old address into the ledger when Allowed. now I can't access my tezos.
  - 0
  - 2020-05-26
  - jared c

1 个回答

投票数

mikereinhart · Answer 1 · 2019-04-17

1

2019-04-17

您的地址很可能是根路径-我建议您尝试不带导出路径的import命令.tezos-client几个月前确实发生了变化:它曾经显示6个导入命令选项-前三个是3个根路径(每个签名路径1个)和3个带有派生路径的路径,即/0'/0'

我怀疑您会使用tezos-client import secret key ledger_yourstruly "ledger://adjective-animal-adjective-animal/ed25519/"

查找丢失的地址

谢谢,但是不,我已经通过蛮力小脚本手动尝试了.但是,我确实注意到您提到的更改.

Thanks, but no, I tried already this manually and through my bruteforce small script. But I do take note of the change that you mention.
- 0
- 2019-04-23
- tndnz
好的,我还有其他可能会有所帮助的东西.不幸的是,由于bash的原因,输入带/不带引号的路径会更改派生地址.我们正在进行调整以防止这种情况,但与此同时,我建议您同时尝试两者.例如: `./tezos-client导入密钥<名称>" ledger:///secp256k1/0'/0'"` 导致PKH不同于 `./tezos-client导入密钥<名称>分类账://://alltheanststuff>/secp256k1/0'/0'

Ok, I have _one_ more thing that may help. Unfortunately due to bash, entering the path with/without quotes changes the derived address. We are making adjustments to prevent this, but in the meantime, I recommend trying both. For instance: `./tezos-client import secret key "ledger:///secp256k1/0'/0'"` results in a different PKH than `./tezos-client import secret key ledger:///secp256k1/0'/0'`
- 0
- 2019-04-24
- mikereinhart
我将再次尝试使用蛮力脚本将其包括在内.如果成功,我会及时通知您.非常感谢您的帮助.

I am going to try agagin my bruteforce script to include this. I will keep you updated if it succeeds. Thanks a lot you for your help.
- 0
- 2019-04-25
- tndnz
让我们知道怎么回事！

Let us know how it goes!
- 0
- 2019-04-30
- mikereinhart