Yes, it would be possible to implement some additional verification mechanisms of the masternode configuration into the program, but after reading the discussion, I begin to conclude that it would not be the best approach. The point is, that the Dash functionalities planned for the coming months will require masternode to provide much greater availability/QoS than it was before. This in turn will face the mn operators to deal with problems that could have been ignored until now, which will require some technical knowledge about the operating system running the Dash daemon and a lot of knowledge about the specifics of the Dash network. People without such knowledge trying to administer masternode sooner or later will get into trouble. For such people, it is probably better to outsource this task to professional vendors (operators). Here I do not mean people who want to learn it, because almost everyone can do it. I mean people who do not want to (because it is beyond their interest) or simply do not have time for it.If not, perhaps it could?
My last attempt to support the v6.x Keepkey firmware ended without success due to bugs in the Keepkey client library that was supposed to support that firmware. I'll check it again, maybe they've fixed the problems since then.Could you make DMT compatible with the latest firmware for the KeepKey? Since the v6.1.0 firmware update, which is the default/stable firmware now, DMT does not recognize that the KeepKey is plugged in.
Can you tell me on which operating system do you use DMT? I'm going to prepare a test version supporting the latest firmware before I release the official version, of course if you are willing to do such tests.Could you make DMT compatible with the latest firmware for the KeepKey? Since the v6.1.0 firmware update, which is the default/stable firmware now, DMT does not recognize that the KeepKey is plugged in.
Test binaries: https://keybase.pub/bertrand256/dash-masternode-tool/executables/0.9.24-hotfix1/Windows 10. I am happy to test.
I ran it and it worked. I was able to vote with my masternode.On Mac, this version works fine with the latest Keepkey firmware. Unfortunately, I could not test it on Windows, because the latest Keepkey bootloader prevents connecting devices to the virtual machines - the only ones I currently have.
If this build does not work for you, please send me the message that appears.
It should only occur if your config file was encrypted before and was created with an older DMT version (having different config file format). In this case, the app converts the file to the latest format during the startup and then immediately saves it, hence that additional "saving" step.The only slightly strange item is that after prompting for the PIN, it then prompted for the decrypt of the config file on the KeepKey, and then it immediately prompted to re-encrypt the config file before prompting again to decrypt and then the main screen popped up. On subsequent runs of the program, it only asked for the decrypt key.
That explains it. I don't believe I have been able to run the latest version since I had updated my firmware on the KeepKey before it came out.It should only occur if your config file was encrypted before and was created with an older DMT version (having different config file format). In this case, the app converts the file to the latest format during the startup and then immediately saves it, hence that additional "saving" step.
On some Windows stations, such errors began to appear recently, also for Trezor. I do not know what the cause is yet, but it seems to me that they are related to some Windows updates. Can you check if Dash Electrum works properly with your Keepkey?Hi, I am getting
Configuration file read error: LIBUSB_ERROR_ACCESS[-3]
on startup with the latest KeepKey firmware of 6.2.0. I checked both with v0.9.25 and v0.9.25 hotfix2.
Yes, I completely agree with that. Actually, for a long time I was planning to change the way data is presented in the main program window, but something has always been more important. I will try to implement it in the future, but currently - as I only develop the app after hours - I can't promise when.I've been thinking about the DMT startup screen. For people with just a few nodes, I think the first window they see should be a summary of balances, totals and recent date-times. All that configuration stuff is, of course, essential, but for most times it's static and irrelevant.
HiI tried another trezor one and trezor T, the masternode tool also can't recognise them. My system is Windows 10. But when I tried masternode tool on my imac the trezors can be recognised.
Both masternode tool and trezor have been updated.