Bertrand256 about dash-masternode-tool HOT 17 CLOSED

Yes, I see this behavior playing around with settings. I was entering my pin as my passphrase (so an incorrect passphrase) and was under the impression it was accepting it because I didn't get any kind of error.

Again, thanks for your help! I will close this ticket.

from dash-masternode-tool.

App Log for MacOS

https://docs.google.com/document/d/1eeJVXEKk2wYW3fZRCaR2tlETmW4cZRrks1-vgvm4yvY/edit?usp=sharing

from dash-masternode-tool.

From your logs, it appears that the Trezor device is busy while DMT is trying to communicate with it. Make sure no other application is running that could be communicating with Trezor, such as Trezor Live, Electrum or even the Brave browser (which also has a built-in hardware wallet interface).

from dash-masternode-tool.

Thank you for this.

I quit my web browsers and Trezor suite, and then connected my Trezor to the DMT. It took some time fetching transactions and never connected. I tried again and still did not populate my transactions. I am curious because I use Trezor suite. I am always sure it is quit before connecting to DMT. I do not have Electrum or Brave browser. What else could be communicating with my Trezor?

Here is the log from today:

2022-09-22 08:12:23 INFO|root|MainThread|app_config.py|init|===========================================================================
2022-09-22 08:12:23 INFO|root|MainThread|app_config.py|init|Application started (v 0.9.32)
2022-09-22 08:12:23 INFO|root|MainThread|app_config.py|init|Environment:
2022-09-22 08:12:23 INFO|root|MainThread|app_config.py|init|environ({'USER': 'katieelliott', '__CFBundleIdentifier': 'DashMasternodeTool', 'COMMAND_MODE': 'unix2003', 'LOGNAME': 'katieelliott', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'SSH_AUTH_SOCK': '/private/tmp/com.apple.launchd.eVAAFlM1qJ/Listeners', 'SHELL': '/bin/bash', 'HOME': '/Users/katieelliott', '__CF_USER_TEXT_ENCODING': '0x1F5:0x0:0x0', 'TMPDIR': '/var/folders/fv/w5d8r1bs1ys58xy723cqgyv00000gn/T/', 'XPC_SERVICE_NAME': '0', 'XPC_FLAGS': '0x0', 'QT_PLUGIN_PATH': '/var/folders/fv/w5d8r1bs1ys58xy723cqgyv00000gn/T/_MEIeeJuot/PyQt5/Qt5/plugins', 'QML2_IMPORT_PATH': '/var/folders/fv/w5d8r1bs1ys58xy723cqgyv00000gn/T/_MEIeeJuot/PyQt5/Qt5/qml', 'TCL_LIBRARY': '/var/folders/fv/w5d8r1bs1ys58xy723cqgyv00000gn/T/_MEIeeJuot/tcl', 'TK_LIBRARY': '/var/folders/fv/w5d8r1bs1ys58xy723cqgyv00000gn/T/_MEIeeJuot/tk', 'QT_API': 'pyqt5'})
2022-09-22 08:12:24 INFO|root|MainThread|main_dlg.py|setupUi|Finished setup of the main dialog.
2022-09-22 08:35:00 INFO|root|MainThread|app_config.py|init|===========================================================================
2022-09-22 08:35:00 INFO|root|MainThread|app_config.py|init|Application started (v 0.9.32)
2022-09-22 08:35:00 INFO|root|MainThread|app_config.py|init|Environment:
2022-09-22 08:35:00 INFO|root|MainThread|app_config.py|init|environ({'USER': 'katieelliott', '__CFBundleIdentifier': 'DashMasternodeTool', 'COMMAND_MODE': 'unix2003', 'LOGNAME': 'katieelliott', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'SSH_AUTH_SOCK': '/private/tmp/com.apple.launchd.T2jfiZDmxA/Listeners', 'SHELL': '/bin/bash', 'HOME': '/Users/katieelliott', '__CF_USER_TEXT_ENCODING': '0x1F5:0x0:0x0', 'TMPDIR': '/var/folders/fv/w5d8r1bs1ys58xy723cqgyv00000gn/T/', 'XPC_SERVICE_NAME': '0', 'XPC_FLAGS': '0x0', 'QT_PLUGIN_PATH': '/var/folders/fv/w5d8r1bs1ys58xy723cqgyv00000gn/T/_MEIJi6zCZ/PyQt5/Qt5/plugins', 'QML2_IMPORT_PATH': '/var/folders/fv/w5d8r1bs1ys58xy723cqgyv00000gn/T/_MEIJi6zCZ/PyQt5/Qt5/qml', 'TCL_LIBRARY': '/var/folders/fv/w5d8r1bs1ys58xy723cqgyv00000gn/T/_MEIJi6zCZ/tcl', 'TK_LIBRARY': '/var/folders/fv/w5d8r1bs1ys58xy723cqgyv00000gn/T/_MEIJi6zCZ/tk', 'QT_API': 'pyqt5'})
2022-09-22 08:35:02 INFO|root|MainThread|main_dlg.py|setupUi|Finished setup of the main dialog.

from dash-masternode-tool.

I apologize for the delay, but I've been testing various things because I'm having trouble identifying what might be the cause.

I have a few questions:

1. Please confirm if I understood correctly that the problem occurs on both Mac and Windows.
2. Are these Mac and Windows separate computers, or are they the same machine?
3. Does the Trezor Live app work correctly with the same Trezor device, i.e. does it show the balances you expect?
4. Have you tried changing Trezor's USB cable to a different one?

from dash-masternode-tool.

Yes it occurs on both Mac & Windows. Separate computers. This is two isolated cases. I help manage a different user through video, screen-share help. They have their own Trezor and use Windows. I have my Mac computer and my Trezor. I do not have has much freedom to trouble shoot on the Windows. So when I refer to mine and "I", I am using Mac.

Yes the Trezor suite is showing balances expected for both users.

A different USB cable is giving me the same result, no transactions.

Additional information. I downloaded the DMT onto a different Mac and had the same problem. Also, I have 2 Trezors here with me to connect to the Macs. One Trezor is connecting fine.

from dash-masternode-tool.

Additional information. I downloaded the DMT onto a different Mac and had the same problem. Also, I have 2 Trezors here with me to connect to the Macs. One Trezor is connecting fine.

Just to be sure: does the other Trezor work correctly with the DMT application on your Mac, in particular, does it show the correct balances? Do both Trezors have the same seed configured?

What is the firmware version of this non-working Trezor? You can read it from within Trezor Live.
Thanks.

from dash-masternode-tool.

Two different Trezors. Two different seed configurations. One works as expected in the DTM, the balances are what is expected. One does not (no transactions found).

I am running firmware v 1.11.2

from dash-masternode-tool.

The issue is so problematic that you will need to compare the Dash addresses that DMT shows with the address that Trezor Suite shows for the same index. If you can do that it would be great. Just remember that Trezor Suite and DMT should not be running at the same time. Below I show with images what steps you should follow.

1. First, open wallet in DMT

2. Read the Dash address for index 0/0
   

3. Close DMT and start Trezor Suite. The only way I have found that allows you to read the Dash address for a specific index in this application is to use the message signing feature, so run it:
   

4. Select the address for index 0:
   

5. Reveal the whole address:
   

6. Get the address and compare it with the one you've got in step 2:
   

Please let me know whether the addresses from step 2 and 6 are equal or not. Do not paste anything private here, such as your real Dash addresses.

from dash-masternode-tool.

They do not match.

I have 6 Dash accounts in my Trezor suite. The DMT is only showing account #1 and addresses. Just to be sure, none of the 6 accounts match the 0/0 in the DMT.

Thank you for digging into this!

from dash-masternode-tool.

Checking in.

Would restoring the Trezor and starting from scratch with my recovery seed do the trick?

Thank you!

from dash-masternode-tool.

Oops, thanks for the reminder.

Would restoring the Trezor and starting from scratch with my recovery seed do the trick?

Unfortunately this is unlikely to help, but what I was going to ask you is whether you use passphrase for your trezor and if so, does it have any non-English (i.e. non ASCII) characters?

from dash-masternode-tool.

I do not use a passphrase, but sometimes it does ask me for one. When it does, I enter my pin as the passphrase. It seemingly accepts it.

from dash-masternode-tool.

Here is probably the cause of the problem. The point is that the passphrase used in hardware wallets (BIP39) works differently than a typical password to protect access to something. Generally, any passphrase will be correct, because any passphrase opens a kind of hidden wallet, giving you completely different set of Dash addresses for each passphrase. Here's an article describing how it works: https://blog.trezor.io/passphrase-the-ultimate-protection-for-your-accounts-3a311990925b.

What's puzzling is why, as you've written, sometimes it asks for a password and sometimes it doesn't. It's a configuration option and if it's not set, the passphrase dialog shouldn't come up. I suggest you check the status of this setting.

This can be done from DMT by following these steps:

1. Click the Toolbox button
   

2. Then click Hardware wallet settings
   

3. And finally, you will see all the settings of your Trezor
   

Note whether the Passphrase option is on or off. If it's off and the app nevertheless sometimes asks for a passphrase, it means there's most likely a problem with either the device or the firmware - the passphrase dialog is invoked by the Trezor library, so it probably isn't related to DMT itself.

Regardless, the next time the app asks you for a passphrase, do not enter your PIN (or anything else) but instead leave the passphrase field blank. The effect will be as if you had the password option disabled.

Btw. does the Trezor suite also sometimes ask you for passphrase or never?

from dash-masternode-tool.

🎉🎉🎉

Passphrase was enabled. I disabled it in the hardware settings. PROBLEM SOLVED! I really appreciate your responsiveness and working with me on this. MUCH gratitude, thank you!

When passphrase was enabled in the DMT, the Trezor Suite requested me to select wallet type (see attached image). If I chose Standard wallet, no passphrase was needed. I confirmed: changing the passphrase setting in the DMT automatically changed the settings in the Trezor suite. Once passphrase was disabled, the Trezor Suit no longer asked for my wallet type.

from dash-masternode-tool.

Also, I tried to just skip the passphrase without disabling the setting. I x'd out of the passphrase box. The DMT would not let me continue. It gives me a cancelled notification.

from dash-masternode-tool.

Also, I tried to just skip the passphrase without disabling the setting. I x'd out of the passphrase box. The DMT would not let me continue. It gives me a cancelled notification.

Stopping with an error is intentional in such a situation. If the user has the password option enabled for their Trezor, then they must enter it, even if it were a blank password. Trying to bypass the password by clicking "cancel" is treated as an abandonment of performing this operation at this point.

We are dealing with financial assets here, so the device must be sure that the user knows what he is doing. In such a situation, it is better to enter a blank passphrase and confirm it with the OK button - then it will behave as if he had the passphrase option turned off.

from dash-masternode-tool.