I've posted some comments on Discord.
I will look at it today, although I can there may be a small problem with it, because I do not have such evo-MN earning transaction (i.e. coinbase UTXO) available on mainnet wallet and Dash testnet isn't supported by Ledger.
DashMaternodeTool v0.9.39 released
Binaries: https://github.com/Bertrand256/dash-masternode-tool/releases/tag/v0.9.39
Changes
Adapting to changes introduced in Dash v21 API (what resolves issues related to wallet and transactions)
Adapting the payment queue calculation & proposal window to the...
At this point, I do not have sufficient knowledge of what specific operations need to be performed with the private key associated with the withdrawal address residing in hardware wallets to declare that DMT will be able to potentially (i.e., after appropriate changes) handle this situation...
I will pay attention to this before publishing the next version, although for now it seems to me that it is implemented correctly. This effect could also have occurred because of the difference in your masternode information between the RPC node to which DMT was connected at the time and the one...
This issue was likely related to another issue on the RPC node (specifically the 'protx update_service_evo' command) that has just been resolved. Please let me know if the "Error occurred while decrypting message" problem reappears, as it would mean that these issues were not related after all...
Sorry for the delay.
First, I would suggest checking if there are any entries in the log with the ERROR level. If there are, please send me the information to one of the contact entries appearing on the Tools->Show contact information form.
If there is nothing like this in the log, I suggest...
DashMaternodeTool v0.9.38 released
Binaries: https://github.com/Bertrand256/dash-masternode-tool/releases/tag/v0.9.38
Changes:
Support for Dash v20 nodes.
It was entirely my fault: I simply underestimated the time needed to prepare a v20 dashd custom build for the RPC node. The rest is an accumulation of various technical problems, from library version incompatibilities to nodes getting stuck in synchronization with the blockchain.
Anyway, the...
I've just published a new version with the above fix: https://www.dash.org/forum/index.php?threads/gui-tool-for-running-masternode-with-trezor.13748/post-236269
DashMaternodeTool v0.9.37 released
Binaries: https://github.com/Bertrand256/dash-masternode-tool/releases/tag/v0.9.37
Changes:
Added the "Legacy operator key" option to the "Update Payout Address" and "Update Voting Key" windows.
Background...
I've created a dedicated build for Windows with the "legacy mode" option availablem, which you can download with the Keybase app under the following link: keybase://public/bertrand256/dash-masternode-tool/executables/0.9.37-rc1/DashMasternodeTool-0.9.37.rc1.zip
See if this helps in your...
1. Are you using a public RPC node or your own to connect to the Dash network?
2. Are you using a legacy operator key? In other words: did you register masternode before Dash v19 was activated?
DashMaternodeTool v0.9.36 released
Binaries: https://github.com/Bertrand256/dash-masternode-tool/releases/tag/v0.9.36
This release contains consolidated fixes from RC1 and RC2:
Changed masternode naming from "HPMN" to "Evolution" to be consistent with the official docs.
Workaround for a Qt...
DashMaternodeTool v0.9.36 RC2 released
Binaries: https://github.com/Bertrand256/dash-masternode-tool/releases/tag/v0.9.36-rc2
Changes:
Changed masternode naming from "HPMN" to "Evolution" to be consistent with the official docs.
Workaround for a Qt 5.15 bug on Windows causing the app to...
The scenario you're describing goes far beyond the realm of Dash and cryptocurrencies in general, because virtually any tool that helps in some activity that is used by a significant percentage of a certain population (whether it be the Trezor wallet, Discord messenger, Dash forum, or even the...
Here's why, for now, I'm not even considering implementing this:
I have communicated both in the application documentation and in my various statements that no such logging is taking place, and I have absolutely no intention of breaking the given promise.
I don't see how collecting such...