New version (0.9.5) of DashMasternodeTool has been released with the following main improvements:
- Fixed connectivity issues ("Sent request" error).
- New RPC connectivity features.
- Feature of finding coallteral transaction/index (Lookup button)
As for networking, I've used a quite different approach in the area of connection between DMT and JSON-RPC daemons. In addition to the new feature of connection over SSL, now you can define more than one connection, so in case of problems with one RPC node, the app will automatically switch to another.
Those, who don't like to or can't run his own JSON-RPC node, just to make some occasionally masternode management, can use "public" nodes, provided by me and @chaeplin
The new version of DMT automatically adds these three connection to its configuration when starting the first time:
- test.stats.dash.org:8080 (@chaeplin's 3-nodes cluster)
- alice.dash-dmt.eu:8080 (my first node)
- luna.dash-dmt.eu:8080 (my second node)
While creating these config entries, app makes the following assumptions:
- if you had a "RPC over SSH" connection type in your old DMT version, the app assumes, that you would probably prefer to connect with your own SSH node, so newly added "public" entries are initially disabled
- if you had a "direct RPC" connection before, the app assumes, that it was probably your local DashQT and that it would rather be more convenient to use "public" nodes, so it disables your old entry and enables new ones
Regardless of whether these assumptions are correct or not, please revise your configuration after running the new version for the first time.
From a clients' security perspective, it is worth to mention, that all (@chaeplin
's and mine) nodes do not log any RPC commands flowing through them. Solution is based on NGINX server and LUA script, available on @chaeplin
;s Github account: https://github.com/chaeplin/dash-ticker/blob/master/web/nginx/dash-jsonrpc-access.lua
I will not encourage or discourage from using these new RPC connectivity options. The only reason I made that effort, was to help not tech-savvy people.
If you delete the default "public" nodes configuration but then you'll want to restore it, here is connection string, which you can paste into "Connections" area of the "Configuration" window:
Passwords are encoded, but not secret (you can see them from the app), but I prefer not to place them on the web as plain-text.
Unfortunately, I am not able to thoroughly test the application on three major operating systems, so if you find a bug, please report it via the Github project page: https://github.com/Bertrand256/dash-masternode-tool/issues
Config file is located in the following folder:
Before saving configuration, applications copies old config.ini to the "backup" subdirectory, appending date/time string to its name.
And finally, I'm sorry for all my spelling errors.