Walletwasabi: model t wasabi help

[gsud247]

2020-06-01 09:32:42 ERROR ConnectHardwareWalletViewModel (140) System.Threading.Tasks.TaskCanceledException: A task was canceled

this is the error message i received. i recovered my model t from see, built wasabi from source on mac os. i clicked search for hardware wallets and am prompted to enter passphrase on model t. after entering passphrase the wallet keeps "searching for device" then task is canceled.

i treid on trezor model one as well and it is not found by wasabi.. just searches forever

[MaxHillebrand]

What is your version of Wasabi and Trezor firmware?

[gsud247]

Trezor 2.3

Wasabi built from source..

Sent from ProtonMail Mobile

On Mon, Jun 1, 2020 at 1:12 PM, Max Hillebrand [e-mail] wrote:

What is your version of Wasabi and Trezor firmware?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

[molnard]

Do you use a passphrase?

[gsud247]

Yes, passphrase is forced onto model t device only

Sent from ProtonMail Mobile

On Mon, Jun 1, 2020 at 2:31 PM, Dávid Molnár [e-mail] wrote:

Do you use a passphrase?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

[gsud247]

The model t prompts me to enter the passphrase. Once i do, the wasabi interface keeps searching for hardware device and eventually I get the error message.

[molnard]

I will get my trezor and test it tomorrow. It was working that is for sure. Keep you updated.

[gsud247]

I also tested it a few weeks back and it was working.

Sent from ProtonMail Mobile

On Tue, Jun 2, 2020 at 11:01 AM, Dávid Molnár [e-mail] wrote:

I will get my trezor and test it tomorrow. It was working that is for sure. Keep you updated.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

[gsud247]

I did use the trezorctl to force passphrase on device. Could that be the issue?

Sent from ProtonMail Mobile

On Tue, Jun 2, 2020 at 11:01 AM, Dávid Molnár [e-mail] wrote:

I will get my trezor and test it tomorrow. It was working that is for sure. Keep you updated.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

[yahiheb]

@molnard there is a new HWI release https://github.com/bitcoin-core/HWI/releases/tag/1.1.1

[molnard]

I tested it using the same version you did @gsud247. It is working for me. However, I am not familiar with forcing the passphrase on device option. It can be, can you try disabling it?

[gsud247]

I wiped the trezor, restored from seed and tried again. Same error message. It does prompt me to enter passphrase but nothing happens after that.

Sent from ProtonMail Mobile

On Wed, Jun 3, 2020 at 4:34 AM, Dávid Molnár [e-mail] wrote:

I tested it using the same version you did @gsud247. It is working for me. However, I am not familiar with forcing the passphrase on device option. It can be, can you try disabling it?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

[gsud247]

I also tested it on my ledger nano x and im having the same problem.

Sent from ProtonMail Mobile

On Wed, Jun 3, 2020 at 4:34 AM, Dávid Molnár [e-mail] wrote:

I tested it using the same version you did @gsud247. It is working for me. However, I am not familiar with forcing the passphrase on device option. It can be, can you try disabling it?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

[molnard]

What changed when it was stopped working? I was struggling for weeks with CC then finally turned out the USB cable was faulty.

[gsud247]

the only thing that had changed is a wipe of the trezor device, and a restore from seed

I just deleted wasabi and rebuilt from source. I also wiped the model t and recovered the seed with passphrase enabled. I just tried with 2 different USBs. This is the error I received once again.

2020-06-04 09:59:04 ERROR ConnectHardwareWalletViewModel (140) System.Threading.Tasks.TaskCanceledException: A task was canceled.
Please confirm action on your Trezor device
2020-06-04 10:07:16 INFO WasabiSynchronizer (267) Downloaded filter for block 633033.
2020-06-04 10:07:39 ERROR ConnectHardwareWalletViewModel (140) System.Threading.Tasks.TaskCanceledException: A task was canceled.
2020-06-04 10:08:17 INFO WasabiSynchronizer (267) Downloaded filter for block 633034.

I do notice this, when I first encountered this proble, I could see the Trezor Model T in the UI after pressing "search hardware wallets" ..... now when i press search hardware wallets I dont see anything in the UI that names the Trezor, however, I am prompted to eneter the passphrase on the Model T device.

[gsud247]

after entering the passphrase, error message

[molnard]

Just a shot in the dark but you can try with this updated HWI: https://github.com/zkSNACKs/WalletWasabi/pull/3725

[gsud247]

Ok, can i do this w/

Git pull ?

Sent from ProtonMail Mobile

On Thu, Jun 4, 2020 at 11:02 AM, Dávid Molnár [e-mail] wrote:

Just a shot in the dark but you can try with this updated HWI: #3725

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

[yahiheb]

https://docs.wasabiwallet.io/using-wasabi/BuildSource.html#check-out-a-developer-branch

Or simply do this:

git fetch origin pull/3725/head:Features/Update-HWI
git checkout Features/Update-HWI
dotnet run

You have to be in the WalletWasabi.Gui folder in order for the last command to work.

Always be careful when testing other branches.

[gsud247]

ok i did that... but..

Please confirm action on your Trezor device
2020-06-04 12:59:52 ERROR ConnectHardwareWalletViewModel (140) System.Threading.Tasks.TaskCanceledException: A task was canceled.

same result

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, June 4, 2020 11:59 AM, yahiheb [e-mail] wrote:

https://docs.wasabiwallet.io/using-wasabi/BuildSource.html#check-out-a-developer-branch

Or simply do this:

git fetch origin pull/3725/head:Features/Update-HWI
git checkout Features/Update-HWI
dotnet run

You have to be in the WalletWasabi.Gui folder in order for the last command to work.

Always be careful when testing other branches.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

[gsud247]

I run bitcoin only firmware on the model t

Sent from ProtonMail Mobile

On Thu, Jun 4, 2020 at 1:01 PM, [e-mail] wrote:

ok i did that... but..

Please confirm action on your Trezor device
2020-06-04 12:59:52 ERROR ConnectHardwareWalletViewModel (140) System.Threading.Tasks.TaskCanceledException: A task was canceled.

same result

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, June 4, 2020 11:59 AM, yahiheb [e-mail] wrote:

https://docs.wasabiwallet.io/using-wasabi/BuildSource.html#check-out-a-developer-branch

Or simply do this:

git fetch origin pull/3725/head:Features/Update-HWI
git checkout Features/Update-HWI
dotnet run

You have to be in the WalletWasabi.Gui folder in order for the last command to work.

Always be careful when testing other branches.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

[molnard]

Wasabi is using HWI as an underlying component to communicate with HW wallets. Your problem seems to be a specific issue on your side. I will keep this in my mind but I cannot reproduce it - and don't see how to move forward. So I would say start a parallel debug procedure here too:

HWI repository is here:
https://github.com/bitcoin-core/HWI/issues

Probably @achow101 has some idea.

Note that there is a known issue with Trezor v2.3.1 latest firmware, that came up recently. It is independent to your issue.

[gsud247]

Will do.

Sent from ProtonMail Mobile

On Fri, Jun 5, 2020 at 8:49 AM, Dávid Molnár [e-mail] wrote:

Wasabi is using HWI as an underlying component to communicate with HW wallets. Your problem seems to be a specific issue on your side. I will keep this in my mind but I cannot reproduce it - and don't see how to move forward. So I would say start a parallel debug procedure here too:

HWI repository is here:
https://github.com/bitcoin-core/HWI/issues

Probably @achow101 has some idea.

Note that there is a known issue with Trezor v2.3.1 latest firmware, that came up recently. It is independent to your issue.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

[molnard]

You can also go down to low-level with this, that would help the debug.

• Open a terminal
• Go to Wasabi repo => WalletWasabi/WalletWasabi/Microservices/Binaries/osx64
• Enter to terminal: ./hwi enumerate
• If you get [ ] - then nothing is connected
• Now you can connect Trezor and enumerate again.

Let's see what happens.

[gsud247]

how exactly do i access the repo? do i just paste:

WalletWasabi/WalletWasabi/Microservices/Binaries/osx64

into the terminal?

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, June 5, 2020 9:15 AM, Dávid Molnár [e-mail] wrote:

You can also go down to low-level with this, that would help the debug.

• Open a terminal

• Go to Wasabi repo => WalletWasabi/WalletWasabi/Microservices/Binaries/osx64

• Enter to terminal: ./hwi enumerate

• If you get [ ] - then nothing is connected

• Now you can connect Trezor and enumerate again.

Let's see what happens.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

[yahiheb]

Open the terminal, and navigate to the WalletWasabi/WalletWasabi/Microservices/Binaries/osx64 folder inside the cloned repository.

[MaxHillebrand]

@gsud247 open the terminal, and then type in the change directory command:
cd WalletWasabi/WalletWasabi/Microservices/Binaries/osx64

[You see @yahiheb, user doesn't know how to cd... :wink:]

[gsud247]

ok... i got into..

WalletWasabi/WalletWasabi/Microservices/Binaries/osx64

then i entered..

./hwi enumerate

i then get:

Please confirm action on your Trezor device

i enter an arbitrary passphrase.. then..

nothing

[gsud247]

by "nothing" i mean once i press the green checkmark on the passphrase prompt on model t device... nothing happens in the terminal at all and the model t goes back to its home screen

[gsud247]

also, i do not have a "pin set" on the trezor device

[molnard]

I am writing it to here too. Wasabi is not compatible with fw v2.3.1. Downgrade it to v2.3.0 to continue debug this.

[molnard]

I am getting this as a result:

Balint-MacBook-Air:osx64 molnardavid$ ./hwi enumerate
Please confirm action on your Trezor device
[{"type": "trezor", "path": "webusb:020:2", "model": "trezor_t", "needs_pin_sent": false, "needs_passphrase_sent": false, "fingerprint": "4433c205"}]
Balint-MacBook-Air:osx64 molnardavid$ 

It is working for me. So this is something with your computer, your trezor and hwi. So lets continue the conversation there. This is not related to Wasabi direcly.

[molnard]

Closing according to https://github.com/bitcoin-core/HWI/issues/339#issuecomment-641909023