• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

GUI tool for running Masternode with Trezor

Hallo, ich bin ganz neu hier,
Gibt es einen Schritt für Schritt Anleitung, wie ich das ganze für Windows installieren muss? Ich will nicht DASH verlieren, wenn ich etwas falsch mache
 
Hallo, ich bin ganz neu hier,
Gibt es einen Schritt für Schritt Anleitung, wie ich das ganze für Windows installieren muss? Ich will nicht DASH verlieren, wenn ich etwas falsch mache
Hallo Christian,

Willkommen im Forum. @tungfa hat eine Anleitung erstellt, diese ist allerdings auf Englisch. Da ein Trezor verwendet wird ist es quasi unmöglich das Deine Dash verloren gehen - sofern Du die Passphrase Deines Trezor nicht verlierst. Ich möchte Dir empfehlen den Dash Nation Slack beizutreten, dort gibt es auch einen Deutschen Kanal und User die Dir sicher weiterhelfen werden.

--> http://dash-nation-invite.herokuapp.com/

Holger
 
When trying to use the latest version of this tool I get as far as "Configure Dash daemon connection in DMT"

When I "Test Connection I get the error:
Connect error. Details: [WinError 10061] No connection could be made because the target machine actively refused it.

Any ideas?

(following this guide: https://github.com/Bertrand256/dash-masternode-tool)
 
Connect error. Details: [WinError 10061] No connection could be made because the target machine actively refused it.
It looks like you don't have RPC listening enabled in dash.conf file of your dash daemon or IP address of your PC is not allowed to communicate with it.

What Dash daemon are you using: DashQT on your local machine or dahsd on remote server?
 
It looks like you don't have RPC listening enabled in dash.conf file of your dash daemon or IP address of your PC is not allowed to communicate with it.

What Dash daemon are you using: DashQT on your local machine or dahsd on remote server?
Dash Qt on local machine. I added the config to the dash.conf and added the same RPC information into DMT.

Dash Qt was running and fully sync'd when I tested connection.
 
If your DashQT runs on the same PC as DMT and following params are set as below:
- rpcbind=0.0.0.0
- rpcport=9998
- rpcallowip=127.0.0.1
- server=1

then within DMT you should choose "Dashd direct RPC" option and set following parameters:
IP: 127.0.0.1
Port: 9998

Is that, what you have set?

BTW. A new (easier for newbies) version of DMT, which I promised last time, is a bit delayed. I hope it will be ready till next Sunday.
 
- rpcbind=0.0.0.0
- rpcport=9998
- rpcallowip=127.0.0.1
- server=1

then within DMT you should choose "Dashd direct RPC" option and set following parameters:
IP: 127.0.0.1
Port: 9998

Yes, same PC.
I didn't have the line rpcbind (not in guide) but I have closed everything, added it and tried again. Still same error.
 
Yes, same PC.
I didn't have the line rpcbind (not in guide) but I have closed everything, added it and tried again. Still same error.

Make sure, that you are editing the same dash.conf file as DashQT is reading: from DashQT choose "Tools->Open wallet configuration file" menu item. The file opened in editor should have all the parameters you filled in.

If the file is correct, the only thing that comes to my mind now is the antivirus/firewall program not allowing DashQT to listen on a certain TCP port.
 
Make sure, that you are editing the same dash.conf file as DashQT is reading: from DashQT choose "Tools->Open wallet configuration file" menu item. The file opened in editor should have all the parameters you filled in.

If the file is correct, the only thing that comes to my mind now is the antivirus/firewall program not allowing DashQT to listen on a certain TCP port.
I had done this "Tools->Open wallet configuration file" and all looks fine.
I tried just disabling my firewall to test it and I still got the same error. I only have windows defender, or whatever they call it theses days, so I doubt that is blocking it.
 
I had done this "Tools->Open wallet configuration file" and all looks fine.
I tried just disabling my firewall to test it and I still got the same error. I only have windows defender, or whatever they call it theses days, so I doubt that is blocking it.
I'll send you another suggestions with pm.
 
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)
dmt-connections.png


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:

[
{
"port": "8080",
"use_ssh_tunnel": false,
"password": "674141414141425a4565533367775a4838415369696478365958416e6d6d646d6c614f7435346b7272352d5879767a366b727076464d344e5162385244356d6856784257686d494d6c426d4d514d526146753948665a314457652d6257564c336d673d3d",
"username": "dmtuser",
"host": "alice.dash-dmt.eu",
"use_ssl": true
},
{
"port": "8080",
"use_ssh_tunnel": false,
"password": "674141414141425a456553334c7044464b525f76736b37763648697a414b796d4f4f647a313764624f386e446b4132475867795648506945355235306c75626457674a452d7950334a3071657253727961423038787763624932327278657a6c33673d3d",
"username": "dmtuser",
"host": "luna.dash-dmt.eu",
"use_ssl": true
},
{
"port": "8080",
"use_ssh_tunnel": false,
"password": "674141414141425a45655333324d527145616241526e6442552d5658685f4a334373657579766d6f4962433843463579744e5f436a72595a4a6c686e5841725f3267417951596f344f41717752764c6a6e37436a763672643650644f68446d7963413d3d",
"username": "dashmnb",
"host": "test.stats.dash.org",
"use_ssl": true
}
]

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:
Windows: C:\Users\<UserName>\DashMasternodeTool\config.ini
Mac: /Users/<UserName>/DashMasternodeTool/config.ini
Linux: /home/<UserName>/DashMasternodeTool/config.ini

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.

Binaries
Github:
https://github.com/Bertrand256/dash.../v0.9.5/DashMasternodeTool_0.9.5.linux.tar.gz
https://github.com/Bertrand256/dash...nload/v0.9.5/DashMasternodeTool_0.9.5.mac.zip
https://github.com/Bertrand256/dash...oad/v0.9.5/DashMasternodeTool_0.9.5.win32.zip
https://github.com/Bertrand256/dash...oad/v0.9.5/DashMasternodeTool_0.9.5.win64.zip

Keybase:
https://keybase.pub/bertrand256/das...s/0.9.5/DashMasternodeTool_0.9.5.linux.tar.gz
https://keybase.pub/bertrand256/das...tables/0.9.5/DashMasternodeTool_0.9.5.mac.zip
https://keybase.pub/bertrand256/das...bles/0.9.5/DashMasternodeTool_0.9.5.win32.zip
https://keybase.pub/bertrand256/das...bles/0.9.5/DashMasternodeTool_0.9.5.win64.zip
 
I have used your latest version and it was very easy to use. Thanks @Bertrand256
Do you have a proposal for this project? If not, I for one would vote to pay you for your time and effort and cover ongoing costs, however small.
 
@Acedian, I planned this application as a nonprofit project, but if at some point I find that there is a growing discrepancy between what I'm planning to do and what I can do after hours, I will consider submitting a proposal. So thank you in advance for your vote :)
 
I used version 0.9.5 just yesterday to start my Masternode from my KeepKey and everything worked perfectly. I sent you a little gift to the dash address on your profile. Thank you and keep up the excellent work!
 
guides updated - waiting for a pro to double check me :rolleyes:
(new version - easy as pie)
 
Back
Top