btcpayserver / btcpayserver/BTCPayServer.Vault

I cant sign with my bitbox02

Open
#39 37 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
178
Forks
88
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**

Sign the transaction with BTCPay Server Vault

**Your BTCPay Environment (please complete the following information):**

- BTCPay Server Version: V1.2.1.0
- BTCPay Server Vault app version: V2.0.1
- Deployment Method: Manual

**Your local environment (please complete the following information):**

- Your operating system Ubuntu 20.04.3 LTS
- Browser: Firefoy y Brave

**Your hardware wallet details (please complete the following information):**

- Hardware wallet name: Bitbox02
- Hardware wallet version: Bitcoin only
- Hardware wallet firmware, bootloader, microcontroller verisons (where applicable): latest

**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)**

Contributor guide

No contributing guide indexed for this repository

Research direction

No source file, test, or entry point is named in the report. Start by reproducing signing on the testnet setup with a BitBox02 and inspect the reported keypath and device errors; done means a transaction can be signed successfully through BTCPay Vault.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
blockchain, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.