Separate names with a comma.
Please sign up to discuss the most innovative cryptocurrency!
Discussion in 'Projects' started by Bertrand256, Mar 20, 2017.
I'll reach you via DM.
DMT v0.9.22 has been published.
DML registration wizard: the possibility of using public keys
for the operator and Dash addresses for the owner and voting.
Main window: the possibility of displaying private keys in the form
of: Dash address, public key and public key hash (for diagnostics).
Wallet: the possibility of adding/hiding any BIP44 account (use
context menu). Please note, that if there is a gap between the account
added and the last one used (having a transaction history), the
official client app for a given hardware wallet (eg Trezor online
wallet) will not show it.
Wallet: the possibility o hiding accounts.
Wallet: signing messages with any address.
Wallet: showing incoming and not yet confirmed UTXOs (from mempool).
Wallet: initially select the masternode address ("Masternode address"
mode) that is currently selected in the main window.
Main window: the user's role is morphed into three independent
roles - owner, operator and voter - one can choose any combination of
DML registration wizard: support for the 'feeSourceAddress' field
in the protx prepare call (added in Dash Core rc11).
Main window: suport for deterministic masternodes in the masternode
Main window: the visibility of the buttons associated with starting
masternodes depends on the status of DIP3 and Spork 15.
Wallet: improved refreshing of the UTXO list as a result of reading
Proposals: fixed an issue that caused some proposals to not be
Wallet: issues with fetching transactions and showing UTXOs for
BIP44 accounts that are beyond the scope of the standard BIP44
account discovery method.
Fixed several other minor issues.
In the meantime, I've published three versions with quick fixes for a few issues reported by MNOs:
"Deadlock detected" problem when sending a transaction from wallet while new transactions data are being fetched from the network
"Error while broadcasting vote message" problem with voting after DIP3 activation
"Unknown USB interface" error when connecting to Keepkey on Windows
Binary versions of the latest fix are available under the same URL: https://github.com/Bertrand256/dash-masternode-tool/releases/tag/v0.9.22
I have published a document regarding the registration of deterministic masternodes with DMT.
Besides the registration procedure itself, it also addresses some issues that very often appear in the questions asked to me.
DMT v0.9.22-hotfix4 released with support for DIP2 transactions on Keepkey:
Keepkey users who have seen the "Encountered invalid prevhash" error when trying to send a transaction with the DIP2 input should now have it fixed.
DMT v0.9.22-hotfix5 released with support for DIP2 tx inputs on Ledger Nano S:
This compilation solves the "mandatory-script-verify-flag-failed (Signature must be zero for failed CHECK(MULTI)SIG operation)" problem occurring when sending transactions with DIP2 input(s).
DMT v0.9.23 has been published.
Please use this version to review for what proposals you need recast your votes (it removes from the application cache votes sent before the spork 15 activation). It also has a GUI support to change the voting private key, which may be needed by some MNOs.
Here are the main changes in one picture:
DashMasternodeTool v0.9.24 has been published
Support for the "update service" feature (mn IP/port, operator payout address).
Support for the "revoke operator" feature.
Additional encryption (RSA) of data sent over the Internet for protx RPC calls.
Does DMT check for mis-configurations as reported in this thread? If not, perhaps it could?
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.
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. I believe that is because of the USB id change mentioned in their release notes: medium.com/shapeshift-stories/keepkey-release-notes-v6-1-0-2-cad4af2722c0
Thanks for your work on DMT, it makes managing/maintaining masternodes a pleasure!
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.
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.
Windows 10. I am happy to test.
Test binaries: https://keybase.pub/bertrand256/dash-masternode-tool/executables/0.9.24-hotfix1/
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.
I ran it and it worked. I was able to vote with my masternode.
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.
Was there some sort of encryption update/upgrade due to the firmware?
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.
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.
Thanks for all your help on this!