-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I cant sign with my bitbox02 #39
Comments
@elchula76 when trying to spend, can you make sure that in the advanced tab Also since this is testned, can you provide PSBT (when signing, instead of the hardware wallet, select PSBT and at the bottom of the next page paste PSBT content) |
Right now I was messaging with the bitbox02 support because i have the same issue with wasabi and they found these: WalletWasabi/WalletWasabi#6303 May be it helps you. Sorry my poor english. |
I don't believe this is the case, on testnet we are using ping @benma any issue with hwi-2.0.1 ? |
@elchula76 which kind of wallet is it? Segwit or Segwit P2SH? (if you don't know, share an address with us) |
The error message also indicate about |
@NicolasDorier there is no known issue with the BitBox02 in HWI 2.0.1. The error message is a generic message and does not necessarily mean the keypath is wrong. @elchula76 please answer the questions above so we can get more hints. @elchula76 If there is a way to export and post a PSBT that you can't sign, please do so (can also be from a new test wallet for privacy, but it would help a lot with debugging). |
Good morning, The wallet may be single sign segwit, there u have an adress: tb1qhejfmq3mfzgfncwdne7fwpyqx8rqxjw7dyf7j6 |
@elchula76 as I mentioned, you could make a new wallet (seed) to share the seed and a PSBT with us that does not work, so we can take a look. Also please provide this: #39 (comment) |
Account key path: m/84'/1'/0' |
@elchula76 What you did seem right to me. If you can share us #39 (comment) |
Can I use the same wallet? It just a test, i m trying to learn how to create and use a store with btcpay |
yes, you can use same wallet |
Tell me if this is what u need { |
You mean with the BTCPay Server Vault? |
@elchula76 can you copy paste not this, but scroll down and there is some base64 string that you can copy. Look the screen I show you above. |
These one? cHNidP8BAHsBAAAAAscHBGQ1UOPT5XC6wa6PZnnW97/YsiNuWqr3UMmoQebRAAAAAAD/////fb/MQ7n/Czv759PPEG1qDADg33N5z58ZpRJp/6o6al4AAAAAAP////8BFjIAAAAAAAAWABQdJ+2osLpTc+uzhqEDUmQGsXYdNgAAAAAAAQEfuAsAAAAAAAAWABReMGKbAPinXtwLFAWZRBxJi/l+ZAEA3wIAAAAAAQGeZH67YrfH319At0tHdq48vgIgfHbaJYziJJAZ6JZ1LgAAAAAA/f///wK4CwAAAAAAABYAFF4wYpsA+Kde3AsUBZlEHEmL+X5kVCkAAAAAAAAWABS5BLwL0X273P+jSH0EC+z+IkUocQJIMEUCIQDPRymc0/+7GsKXvzoIvvaF4D3rIEdKAgNmZg6SjiVanAIgEWpD9TjA1Xsn2pxPLXYI7kO1k3e38ucMBpRIT4beYn0BIQJwLbmRMEALxLjrsPkL9RqakRoyI+KAKH17TKuUX6TC/gAAAAAiBgPYEJAnPWCJgWm/tUSdRcPO/wPU5pAa49q+1N3nbgUqfRh7hGC8VAAAgAEAAIAAAACAAAAAAAAAAAAAAQEfECcAAAAAAAAWABR+ZUrkb0vwqPQJWT42DUMnAL4kKgEA3wEAAAAAAQFUdW84V+yPnTkPysj0AOsVbVqb+dXcSighOX6qTkFZZAMAAAAA/////wIQJwAAAAAAABYAFH5lSuRvS/Co9AlZPjYNQycAviQq5XkAAAAAAAAWABQ9BMAhn3dpPSEBbHVmEaalMRIf4wJIMEUCIQDwq5CqYnA5e2L47FJr/cBHaBKV90ay2GnHyvziwU/YRgIgHJPWtncK4m2Bpkxf/JMJBz9VvtVuBiF5N7Zo3FrM4qABIQO28z0uYWAa3emF5pruBwuF7jmJTn3UZHcowtOC2N1cEgAAAAAiBgJsTj3wE2JKQWQPPNsHiSpjrLqAIWLHhiAW+aJOARuzyxh7hGC8VAAAgAEAAIAAAACAAAAAAAUAAAAAAA== |
yes thanks one moment please |
it seems to me correct PSBT. |
I dont know if helps u but with specter I have these: Test | Single (Segwit) | m/84h/1h/0h; the same key path and i can send and receive transaction with the same bitbox02. |
@benma it seems his PSBT is correct. Can you take a look at it? (if you use Brave, think of removing the shield) |
I try it with firefox to |
I try the same removing the shield and againg-. Device found: Unknown |
I try to test the bitbox02 at the same link but it doesnt work because the server vault dont work at these link |
@elchula76 I think this is something wrong with the bitbox02 at this point. Let's wait if @benma can repro. |
ok thanks, If i can help u, iḿ here working with your great work. |
@NicolasDorier I ran Any other quick ways to test signing here? @elchula76 can you share your mnemonic seed (if only used for testing purposes)? If not, it would be very helpful if you could make a new seed to share here, and another PSBT that fails, so I can try to figure out what is going on. |
I don't know if helps you but I use the same seed with electrum with mi bitbox02 HWW and it works fine signing the transaction. |
@benma that's strange error, I never saw this. Do you have a stacktrace in the javascript console? I will push a new commit that at least fix the device type btw, is it possible the problem of @elchula76 come from the PSBT not having hte non_witness_utxo filled in? |
I always filled the box of non_witness_utxo, but i never try to sign the transaction with PSBT, I really dont know how it works and I dont know if bitbox02 can... I will try. |
@NicolasDorier I added a testnet bitbox02 wallet, received some coins, made a tx, and I can reproduce the same error. However, when I copy the generated PSBT and run it on the command line like this:
The transaction is displayed on the device and can be signed normally. This means that somehow BTCPayServer.Vault is invoking HWI in the wrong way (maybe missing the |
@NicolasDorier did you get a chance to take a look? As mentioned, the exported PSBT and everything on the HWI side seems okay. |
sorry about this, I forgot this. I'll need to try, but my bitbox2 is at the office. I'll try to get it monday and repro. |
@elchula76 if can you DM me on https://chat.btcpayserver.org/ so I don't drop the ball? |
Done
El vie, 1 oct 2021 a las 15:30, Nicolas Dorier ***@***.***>)
escribió:
… @elchula76 <https://github.com/elchula76> if can you DM me on
https://chat.btcpayserver.org/ so I don't drop the ball?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#39 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVPYKVWLU3CKYX6XEKNNXA3UEWZV5ANCNFSM5DO5TFQQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Describe the bug
Sign the transaction with BTCPay Server Vault
Your BTCPay Environment (please complete the following information):
Your local environment (please complete the following information):
Your hardware wallet details (please complete the following information):
Additional context
Device found: Unknown
An unexpected error happened. (Input error: error code: 103, message: generic error. A keypath might be invalid. Supported keypaths are: m/49'/0'/ for p2wpkh-p2sh; m/84'/0'/ for p2wpkh; m/48'/0'//2' for p2wsh multisig; m/48'/0'//1' for p2wsh-p2sh multisig; m/48'/0'/' for any supported multisig; account can be between 0' and 99'; For address keypaths, append /0/
for a receive and /1/ for a change address.)
I think these is part of the issue, i find it in the report:
3-9:1.0: Failed to open report descriptor at '/sys/devices/pci0000:00/0000:00:14.0/usb3/3-9/3-9:1.0/report_descriptor': No such file or directory
I can receive but I cant spent. Ićant understand that becouse I can do that with Specter. Iḿ running the btcpayserver in a testnet node.
Screenshots / Video / GIf (if applicable)
The text was updated successfully, but these errors were encountered: