Search results

Thanks, I hope that this will make such issues less and less frequent :-)

DashMasternodeTool v0.9.14 released Fixed the 'protocol version' issue occurring when starting masternode just after the "12.1->12.2" upgrade Ability to enter the 'protocol version' value by the user if she/he decides to use non-default value Self-accepting SSL certificates when downloading...

@GrandMasterDash Dashcentral.org accessible from several hours. If you're still getting errors when reading proposal external attributes, you may try this version: https://keybase.pub/bertrand256/dash-masternode-tool/testing/0.9.13.linux-ssl/DashMasternodeTool_0.9.13.linux.tar.gz I've found...

Sorry for the delay. I've uploaded another linux binary, compiled on an older linux version, which I hope resolves the problem. Could you download and try again? URL: https://github.com/Bertrand256/dash-masternode-tool/releases/download/v0.9.13/DashMasternodeTool_0.9.13.linux.tar.gz

This issue is related to problems with accessing dashcentral.org, which is used by the app to download external atrributes (proposal name, owner, etc). BTW, Dashcentral.org is now experiencing problems caused by a serius outage of the OVH infrastructure...

Yes, you can now throw away v0.9.12 and move to v0.9.13, of course, if you are not afraid of "13" in the name :-)

Yes, you have to issue the `Start masternode...` command since your last version seen by the network was 12.1 and now it's 12.2 For this use DMT v0.9.12

Maybe something went wrong during the upgrade. I suppose that you had `dashd` executable inside the `.dashcore` directory (as I wrote earlier) and deleted it after the execution. I suggest you to stop the process and after making sure it's really not running, run it again, making sure, that...

No clue what could be the reason, except running another executable. I assume, that you've checked your running process image path (sudo ls -l /proc/<PID>/exe)

That's the client version and it's ok. What's returned by `dashd --version` command?

It looks like in fact you did not have a new version. You may have unpacked the `dashd` and `dash-cli` files into the `.dashcore` subfolder as suggested one of the documents which I've seen today. Anyway, on my server both files are located above the `.dashcore` directory and node runs v12.2 as...

Problem is temporary and will be resolved after propagation of the information on the Dash network, but I have to consider more reliable method of determining the version of the masternode protocol before next "big update" :-)

I would like to inform you and others about potential problems you may have with starting masternode using DMT 0.9.13. As I mentioned earlier, v0.9.13 reads the protocol version of your masternode from the Dash network. The problem is that it reads this value from the RPC node to which it is...

Oops, sorry, I forgot not to compile it on the latest MacOS - actually it has to be compiled on the oldest Mac OS version used by users (I use High Sierra). Binary updated, please re-download...

DashMasternodeTool v0.9.13 released Full support for Ledger Nano S hardware wallets (including earnings transfer) Consider the masternode protocol version when sending the 'start masternode' message Fix: 'invalid password' message for RPC over SSH connection before even asking the user for a...

As you probably know, migration to v12.2 has already begun. DMT is prepared for it, but there is a small nuance: "start masternode" message format requires passing the masternode's current protocol version into it. In the current DMT version (0.9.12) this value is taken from the RPC node DMT is...

Hi, one of the RPC nodes upgraded, the second left as verion 12.1 for those who for some reason have to send "start masternode" message for their old (v12.1) masternodes. That v12.1 RPC node has its TCP port changed, so DMT with default configuration will skip it while connecting.

When you close the application, the log should be flushed to disk (it's cached at runtime). I probably know what is the error: there is a new proposal with one of the fields with a different data type than expected. I have fixed this already and will release in a day or two along with other...

Ok, great that you located the cause. Thanks for the feedback.

To my Keybase share I have uploaded binaries compiled on two systems: Ubuntu and Manjaro. Both are based on the newest Python - v3.6. Please, give me a feedback whether those files run with or without problems. URL: https://keybase.pub/bertrand256/dash-masternode-tool/testing/DMT%200.9.12-linux/