Search results

DMT v0.9.21 has been published. Binaries: https://github.com/Bertrand256/dash-masternode-tool/releases/tag/v0.9.21 The most important change is the support for deterministic masternodes (Dash v0.13). Notes on starting masternodes. In the period of coexistence of v0.12 and v0.13 nodes, starting...

I have published next DMT beta version with some small fixes: https://github.com/Bertrand256/dash-masternode-tool/releases/tag/v0.9.21-beta5 In addition, I've also prepared a compiled binary of Trezor T emulator, which can be useful for people who only have Keepkey or Ledger Nano S devices...

After a few months of work, I can finally share the first official test version of DMT supporting deterministic masternodes. Binaries: https://github.com/Bertrand256/dash-masternode-tool/releases/tag/v0.9.21-beta4 This version allows you to: perform masternode tests on testnet if the...

Thanks guys for your effort in supporting collaterals controlled by the hardware wallets in the DIP3 implementation. I confirm that I am working on supporting the migration process of MNs to Deterministic MNs in Dash Masternode Tool, mainly to support less tech-savvy users. My goal is the...

I'm sorry, unfortunately not. Access to a physical device of this type would be needed to add the support for it, but unfortunately I do not have one. The good news is that after migrating Dash to v0.13, using DMT will no longer be needed to start MN if collateral is controlled by the hardware...

As tomorrow the declared 3-month period of implementation of my proposal related to the development of the DMT application will end, I wanted to reassure everyone that the work is under way. However, the number of changes that I started turned out to be too large to be closed by the end of...

Here's a great article on this topic: https://blog.dash.org/introducing-deterministic-masternode-lists-daaa7c9bef34

Yes, you can not re-use mn broadcast messages - if the message is the same as the previous one, it is skipped. CMasternodePing part of the masternode broadcast message (CMasternodeBroadcast) is signed with the masternode private key and the rest of the message is signed with the collateral...

The best source, in my opinion, is the official protocol documentation: https://github.com/dashpay/dash/blob/master/dash-docs/protocol-documentation.md#mnannounce---mnb Here's how I implemended it in DashMasternodeTool: Message classes...

I started testing this solution quite recently, so I have not checked all the possible scenarios yet (and there are a lot of them). For now I know, that despite a few restrictions, the case looks quite promising. In a few days I should have quite definitive conclusions.

First of all, check if you have no spaces or other illegal characters in the collateral address. Second thing: make sure you do not have the Trezor online wallet running when signing the start message - it happens often, that another app connected to the same device distorts the data exchanged...

Recently I noticed that @chaeplin stopped maintaining the dashmnb project. I would like to take this opportunity to thank him once again for his great project and remind everyone that DMT core features were based on the dashmnb source code and without it, I probably would not have started this...

In a few days a migration to v12.3 will begin, so it's time for some practical tips related to this process for those of you who use DashMasternodeTool to controll the masternode collateral. DashMasternodeTool version Use the latest DMT version (v0.9.20), which is designed to work with v12.3...

DashMasternodeTool v0.9.20 released. Executable files: https://github.com/Bertrand256/dash-masternode-tool/releases/tag/v0.9.20 In addition to a few minor fixes, most of the changes relate to the upcoming version of Dash v12.3 and changes in the protocol that it introduces.

Thanks for the feedback. More important than the wait time is the number of confirmations. Theoretically, in half an hour you should have at least 6 confirmations, but sometimes it happens that it is not enough, so you need to check the number of confirmations (DMT has a dedicated column for...

You probably was trying to send an UTXO having less that 6 confirmations, which is required for InstantSend. In subsequent versions, I will implement a warning displayed when the user attempts to perform an InstantSend operation without a minimum number of confirmations.

In this case, the error message comes from the RPC node you were connected to - DMT just displayed it. With this message the node referred to his own debug.log file. I will analyze what could be the reason, but it would be helpful it you sent me the app's log file copied after retrying the...

Ha ha, I should have called it "fork masternode" :)

Thanks for the feedback. I would appreciate your help in taking some additional information on your computer with v0.9.10, of course if you have at least one UTXO left: open the configuration window on the 'Miscellaneous' tab change log level to "Debug" open the payment window from the...

DashMasternodeTool v0.9.19 released Executable files: https://github.com/Bertrand256/dash-masternode-tool/releases/tag/v0.9.19 Added InstantSend support in the payment window Duplicate masternode feature (main window) Fixed Deselecting proposals after casting votes Data validation error in...