• 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

@Acedian The risk is, that person who provides JSON-RPC node to the others, could collect information on what RPC commands are sent from what IP and pass that information to some bad guys, who can visit MNo in his/her home (if his IP is static/not behind VPN). However, most people don't realize that, this threat is simmilar to the risk of using "thin" wallets which doesn't hold it's own blockchain but rather rely on some middleman servers, so it applies to most (or all) of mobile wallets, Electrum and other similar apps. If you dont trust the server provider and are able to use your own RPC node, it is better to do so. My and @chaeplin's JSON-RPC nodes doesn't log such a sensitive data, but it is up to the user to believe it or not :)
 
@Acedian The risk is, that person who provides JSON-RPC node to the others, could collect information on what RPC commands are sent from what IP and pass that information to some bad guys, who can visit MNo in his/her home (if his IP is static/not behind VPN).

So, if I use a VPN provided by a reputable company, can I presume I am safe to use DMT including the provided JSON-RPC?
Also, can an IP that is dynamically assigned by an ISP be traced to a home? I know the logs are held by ISPs, but surely this information has to be confidential.
 
@Acedian Scenario I presented is super paranoid. In practice, in order for an IP-address to have some value for criminals, it would be necessary to get the information from a few other companies, which would be quite costly. Of course, if you have a dynamic IP or you use a VPN, it would be even more difficult/expensive.

From my perspective you can safely use the provided JSON-RPC nodes, or if you don't trust me enough (I'm quite new to the Dash community) you can turn-off my two nodes (alice.dash-dmt.eu, luna.dash-dmt.eu) in DMT config and use chaeplin's node, which is very well known and trusted community member without any doubts. His node is: test.status.dash.org

Configuration should then look like:
upload_2017-5-29_16-33-47.png
 
@Acedian I agree with @Bertrand256 - default config should be safe for most cases... but if I still prefer to have things under my own control, especially if that is super easy to do (I already run a node, so all I had to do was reindex with all indexes on). :)
 
Thanks for the wonderful tool @Bertrand256!

I was able to use version 0.9.3 successfully for Masternode setup. However, I am unable to connect using version 0.9.6.

upload_2017-6-11_15-44-44.png

upload_2017-6-11_15-44-12.png
upload_2017-6-11_15-46-0.png


I followed your instructions closely and even re-installed v0.12.1.5 of Dash Core. Any ideas on what I might be doing wrong and how I can get v0.9.6 working? I'd like to take advantage of the new features!
 
@Winston84 This error should occur only if your 'RPC user', 'RPC password' GUI parameters don't match 'rpcuser', 'rpcpassword' from your dash.conf file.
Did you open the dash.conf file by executing Dash Core menu: Tools->Open Wallet Configuration File? This should guarantee openning the correct dash.conf file.
 
Thanks for the wonderful tool @Bertrand256!

I was able to use version 0.9.3 successfully for Masternode setup. However, I am unable to connect using version 0.9.6.

View attachment 4212
View attachment 4211View attachment 4213

I followed your instructions closely and even re-installed v0.12.1.5 of Dash Core. Any ideas on what I might be doing wrong and how I can get v0.9.6 working? I'd like to take advantage of the new features!
@Winston84 This error should occur only if your 'RPC user', 'RPC password' GUI parameters don't match 'rpcuser', 'rpcpassword' from your dash.conf file.
Did you open the dash.conf file by executing Dash Core menu: Tools->Open Wallet Configuration File? This should guarantee openning the correct dash.conf file.

Thanks for the response @Bertrand256. I did access the dash.conf file through the Dash Core menu as you stated above.

upload_2017-6-12_21-29-58.png
upload_2017-6-12_21-31-53.png


I tried both the 64 bit and 32 bit downloads of Version 0.9.6 and neither work for me. However Version 0.9.3 connects without any problem.

upload_2017-6-12_21-37-0.png


I decided to check the other versions as well. I can connect to 0.9.4 but get the same error with 0.9.5.

Any other thoughts on why this might not be working for me? I'm using Windows 7.
 
@Winston84 It seems that the application in your system actually has some problem with passing connection parameters. To track the problem I will prepare a special version with more logging, and then will contact you with PM.

We are probably in quite different time zones, so the solution may take some time, but I'm determined to find the cause.
 
@GrandMasterDash , can you run DMT from a linux terminal and paste here the error message if any shows up?

It's probably a problem with graphic libraries installed with another app interfering with QT libraries used by the DMT, which crashes the app when showing an input file dialog.
 
Two parts.. first of all, here are the messages display when starting DMT. I am trimming this down because the same errors are appearing all over the place...

(DashMasternodeTool-0.9.6:25134): Gtk-WARNING **: Theme parsing error: gtk.css:17:21: '-gtk-outline-radius' is not a valid property name

(DashMasternodeTool-0.9.6:25134): Gtk-WARNING **: Theme parsing error: gtk.css:23:2: Missing name of pseudo-class

(DashMasternodeTool-0.9.6:25134): Gtk-WARNING **: Theme parsing error: gtk.css:35:21: Missing name of pseudo-class

(DashMasternodeTool-0.9.6:25134): Gtk-WARNING **: Theme parsing error: gtk.css:76:6: Missing name of pseudo-class

(DashMasternodeTool-0.9.6:25134): Gtk-WARNING **: Theme parsing error: gtk.css:97:18: '-gtk-icon-shadow' is not a valid property name

(DashMasternodeTool-0.9.6:25134): Gtk-WARNING **: Theme parsing error: gtk.css:113:18: '-gtk-icon-shadow' is not a valid property name

(DashMasternodeTool-0.9.6:25134): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

This likely means that your installation is broken.
Try running the command
gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
to make things work again for the time being.

(DashMasternodeTool-0.9.6:25134): Gtk-WARNING **: Theme parsing error: gtk.css:129:20: Missing name of pseudo-class

(DashMasternodeTool-0.9.6:25134): Gtk-WARNING **: Theme parsing error: gtk.css:133:12: 'min-height' is not a valid property name

(DashMasternodeTool-0.9.6:25134): Gtk-WARNING **: Theme parsing error: gtk.css:145:13: 'caret-color' is not a valid property name

(DashMasternodeTool-0.9.6:25134): Gtk-WARNING **: Theme parsing error: gtk.css:160:14: 'min-height' is not a valid property name

(DashMasternodeTool-0.9.6:25134): Gtk-WARNING **: Theme parsing error: gtk.css:176:8: Missing name of pseudo-class

(DashMasternodeTool-0.9.6:25134): Gtk-WARNING **: Theme parsing error: gtk.css:225:15: Missing name of pseudo-class

(DashMasternodeTool-0.9.6:25134): Gtk-WARNING **: Theme parsing error: gtk.css:304:32: Missing name of pseudo-class

(DashMasternodeTool-0.9.6:25134): Gtk-WARNING **: Theme parsing error: gtk.css:304:32: Missing closing bracket for :not()

(DashMasternodeTool-0.9.6:25134): Gtk-WARNING **: Theme parsing error: gtk.css:312:40: Missing name of pseudo-class

(DashMasternodeTool-0.9.6:25134): Gtk-WARNING **: Theme parsing error: gtk.css:312:40: Missing closing bracket for :not()

(DashMasternodeTool-0.9.6:25134): Gtk-WARNING **: Theme parsing error: gtk.css:334:43: Missing name of pseudo-class

(DashMasternodeTool-0.9.6:25134): Gtk-WARNING **: Theme parsing error: gtk.css:334:43: Missing closing bracket for :not()

(DashMasternodeTool-0.9.6:25134): Gtk-WARNING **: Theme parsing error: gtk.css:342:51: Missing name of pseudo-class

(DashMasternodeTool-0.9.6:25134): Gtk-WARNING **: Theme parsing error: gtk.css:342:51: Missing closing bracket for :not()
 
After pressing the "Import" button I get the following errors... first 100 lines...

*** Error in `path/to/DMT/DashMasternodeTool-0.9.6': malloc(): memory corruption: 0x000000000184baa0 ***
======= Backtrace: =========
/usr/lib/libc.so.6(+0x72bdd)[0x7f2af5700bdd]
/usr/lib/libc.so.6(+0x792ec)[0x7f2af57072ec]
/usr/lib/libc.so.6(+0x7bea1)[0x7f2af5709ea1]
/usr/lib/libc.so.6(__libc_malloc+0x78)[0x7f2af570b6a8]
/tmp/_MEIWOr2kC/libglib-2.0.so.0(g_malloc+0x19)[0x7f2af061c719]
/tmp/_MEIWOr2kC/libgobject-2.0.so.0(g_param_spec_pool_list+0x171)[0x7f2ae45a63b1]
/tmp/_MEIWOr2kC/libgobject-2.0.so.0(+0x14175)[0x7f2ae459e175]
/tmp/_MEIWOr2kC/libgobject-2.0.so.0(+0x2d2cb)[0x7f2ae45b72cb]
/tmp/_MEIWOr2kC/libgobject-2.0.so.0(g_type_class_ref+0x77b)[0x7f2ae45ba2cb]
/tmp/_MEIWOr2kC/libgobject-2.0.so.0(g_object_newv+0x27d)[0x7f2ae45a0dad]
/tmp/_MEIWOr2kC/libgobject-2.0.so.0(g_object_new+0x104)[0x7f2ae45a1534]
/usr/lib/gio/modules/libgioremote-volume-monitor.so(+0x817c)[0x7f2acabfe17c]
/usr/lib/gio/modules/libgioremote-volume-monitor.so(+0xc399)[0x7f2acac02399]
/usr/lib/gio/modules/libgioremote-volume-monitor.so(+0xd2b1)[0x7f2acac032b1]
/tmp/_MEIWOr2kC/libgobject-2.0.so.0(+0x15ad8)[0x7f2ae459fad8]
/tmp/_MEIWOr2kC/libgobject-2.0.so.0(g_object_newv+0xd1)[0x7f2ae45a0c01]
/tmp/_MEIWOr2kC/libgobject-2.0.so.0(g_object_new+0x104)[0x7f2ae45a1534]
/tmp/_MEIWOr2kC/libgio-2.0.so.0(g_volume_monitor_get+0x7c)[0x7f2ae5408ebc]
/tmp/_MEIWOr2kC/libgtk-3.so.0(+0x25c3f5)[0x7f2ae5e593f5]
/tmp/_MEIWOr2kC/libgobject-2.0.so.0(g_type_create_instance+0x1f9)[0x7f2ae45bd359]
/tmp/_MEIWOr2kC/libgobject-2.0.so.0(+0x1531b)[0x7f2ae459f31b]
/tmp/_MEIWOr2kC/libgobject-2.0.so.0(g_object_newv+0xd1)[0x7f2ae45a0c01]
/tmp/_MEIWOr2kC/libgtk-3.so.0(+0x11a75a)[0x7f2ae5d1775a]
/tmp/_MEIWOr2kC/libgtk-3.so.0(+0x11ce73)[0x7f2ae5d19e73]
/tmp/_MEIWOr2kC/libglib-2.0.so.0(+0x4d5a3)[0x7f2af061a5a3]
/tmp/_MEIWOr2kC/libglib-2.0.so.0(g_markup_parse_context_parse+0xfc3)[0x7f2af061b763]
/tmp/_MEIWOr2kC/libgtk-3.so.0(+0x11d8d6)[0x7f2ae5d1a8d6]
/tmp/_MEIWOr2kC/libgtk-3.so.0(gtk_builder_extend_with_template+0x1a8)[0x7f2ae5d15b78]
/tmp/_MEIWOr2kC/libgtk-3.so.0(gtk_widget_init_template+0x107)[0x7f2ae5f5fe27]
/tmp/_MEIWOr2kC/libgtk-3.so.0(+0x1ae4f1)[0x7f2ae5dab4f1]
/tmp/_MEIWOr2kC/libgobject-2.0.so.0(g_type_create_instance+0x1f9)[0x7f2ae45bd359]
/tmp/_MEIWOr2kC/libgobject-2.0.so.0(+0x1531b)[0x7f2ae459f31b]
/tmp/_MEIWOr2kC/libgobject-2.0.so.0(g_object_newv+0xd1)[0x7f2ae45a0c01]
/tmp/_MEIWOr2kC/libgtk-3.so.0(+0x11a75a)[0x7f2ae5d1775a]
/tmp/_MEIWOr2kC/libgtk-3.so.0(+0x11bb65)[0x7f2ae5d18b65]
/tmp/_MEIWOr2kC/libgtk-3.so.0(+0x11d4f1)[0x7f2ae5d1a4f1]
/tmp/_MEIWOr2kC/libglib-2.0.so.0(+0x4d6d7)[0x7f2af061a6d7]
/tmp/_MEIWOr2kC/libglib-2.0.so.0(g_markup_parse_context_parse+0xd8e)[0x7f2af061b52e]
/tmp/_MEIWOr2kC/libgtk-3.so.0(+0x11d8d6)[0x7f2ae5d1a8d6]
/tmp/_MEIWOr2kC/libgtk-3.so.0(gtk_builder_extend_with_template+0x1a8)[0x7f2ae5d15b78]
/tmp/_MEIWOr2kC/libgtk-3.so.0(gtk_widget_init_template+0x107)[0x7f2ae5f5fe27]
/tmp/_MEIWOr2kC/libgtk-3.so.0(+0x1a773e)[0x7f2ae5da473e]
/tmp/_MEIWOr2kC/libgobject-2.0.so.0(g_type_create_instance+0x1f9)[0x7f2ae45bd359]
/tmp/_MEIWOr2kC/libgobject-2.0.so.0(+0x1531b)[0x7f2ae459f31b]
/tmp/_MEIWOr2kC/libgobject-2.0.so.0(g_object_new_valist+0x3b5)[0x7f2ae45a11b5]
/tmp/_MEIWOr2kC/libgobject-2.0.so.0(g_object_new+0xf1)[0x7f2ae45a1521]
/tmp/_MEIWOr2kC/libgtk-3.so.0(gtk_file_chooser_dialog_new+0x74)[0x7f2ae5da5294]
/tmp/_MEIWOr2kC/qt5_plugins/platformthemes/libqgtk3.so(+0x13282)[0x7f2ae653f282]
/tmp/_MEIWOr2kC/qt5_plugins/platformthemes/libqgtk3.so(+0x1749d)[0x7f2ae654349d]
/tmp/_MEIWOr2kC/libQt5Widgets.so.5(_ZNK14QDialogPrivate14platformHelperEv+0x67)[0x7f2aed51c8d7]
/tmp/_MEIWOr2kC/libQt5Widgets.so.5(_ZN18QFileDialogPrivate4initERK4QUrlRK7QStringS5_+0x3b)[0x7f2aed52df9b]
/tmp/_MEIWOr2kC/libQt5Widgets.so.5(_ZN11QFileDialogC1ERK15QFileDialogArgs+0x66)[0x7f2aed52e3c6]
/tmp/_MEIWOr2kC/libQt5Widgets.so.5(_ZN11QFileDialog14getOpenFileUrlEP7QWidgetRK7QStringRK4QUrlS4_PS2_6QFlagsINS_6OptionEERK11QStringList+0x10b)[0x7f2aed52e50b]
/tmp/_MEIWOr2kC/libQt5Widgets.so.5(_ZN11QFileDialog15getOpenFileNameEP7QWidgetRK7QStringS4_S4_PS2_6QFlagsINS_6OptionEE+0x9a)[0x7f2aed52e76a]
/tmp/_MEIWOr2kC/PyQt5.QtWidgets.so(+0x229bd7)[0x7f2aedc4dbd7]
/tmp/_MEIWOr2kC/libpython3.5m.so.1.0(PyCFunction_Call+0xe9)[0x7f2af50a71b9]
/tmp/_MEIWOr2kC/libpython3.5m.so.1.0(PyEval_EvalFrameEx+0x842b)[0x7f2af51c1f5b]
/tmp/_MEIWOr2kC/libpython3.5m.so.1.0(+0x24ac0c)[0x7f2af5251c0c]
/tmp/_MEIWOr2kC/libpython3.5m.so.1.0(PyEval_EvalCodeEx+0x23)[0x7f2af5251ce3]
/tmp/_MEIWOr2kC/libpython3.5m.so.1.0(+0xd2a98)[0x7f2af50d9a98]
/tmp/_MEIWOr2kC/libpython3.5m.so.1.0(PyObject_Call+0x6e)[0x7f2af51808ee]
/tmp/_MEIWOr2kC/libpython3.5m.so.1.0(+0x225a4c)[0x7f2af522ca4c]
/tmp/_MEIWOr2kC/libpython3.5m.so.1.0(PyObject_Call+0x6e)[0x7f2af51808ee]
======= Memory map: ========
00400000-00407000 r-xp 00000000 fe:00 5115243 /path/to/DMT/DashMasternodeTool-0.9.6
00607000-00608000 rw-p 00007000 fe:00 5115243 /path/to/DMT/DashMasternodeTool-0.9.6
00608000-00618000 rw-p 00000000 00:00 0
00793000-018ae000 rw-p 00000000 00:00 0 [heap]
7f2ac4000000-7f2ac402a000 rw-p 00000000 00:00 0
7f2ac402a000-7f2ac8000000 ---p 00000000 00:00 0
7f2acabf6000-7f2acac0f000 r-xp 00000000 fe:00 10884601 /usr/lib/gio/modules/libgioremote-volume-monitor.so
7f2acac0f000-7f2acae0f000 ---p 00019000 fe:00 10884601 /usr/lib/gio/modules/libgioremote-volume-monitor.so
7f2acae0f000-7f2acae12000 r--p 00019000 fe:00 10884601 /usr/lib/gio/modules/libgioremote-volume-monitor.so
7f2acae12000-7f2acae13000 rw-p 0001c000 fe:00 10884601 /usr/lib/gio/modules/libgioremote-volume-monitor.so
7f2acae13000-7f2acafcd000 rw-s 00000000 00:05 13762596 /SYSV00000000 (deleted)
7f2acafcd000-7f2acafd8000 r-xp 00000000 fe:00 9966848 /usr/lib/libnss_nis-2.25.so
7f2acafd8000-7f2acb1d7000 ---p 0000b000 fe:00 9966848 /usr/lib/libnss_nis-2.25.so
7f2acb1d7000-7f2acb1d8000 r--p 0000a000 fe:00 9966848 /usr/lib/libnss_nis-2.25.so
7f2acb1d8000-7f2acb1d9000 rw-p 0000b000 fe:00 9966848 /usr/lib/libnss_nis-2.25.so
7f2acb1d9000-7f2acb1ee000 r-xp 00000000 fe:00 9966846 /usr/lib/libnsl-2.25.so
7f2acb1ee000-7f2acb3ed000 ---p 00015000 fe:00 9966846 /usr/lib/libnsl-2.25.so
7f2acb3ed000-7f2acb3ee000 r--p 00014000 fe:00 9966846 /usr/lib/libnsl-2.25.so
7f2acb3ee000-7f2acb3ef000 rw-p 00015000 fe:00 9966846 /usr/lib/libnsl-2.25.so
7f2acb3ef000-7f2acb3f1000 rw-p 00000000 00:00 0
7f2acb3f1000-7f2acb3f8000 r-xp 00000000 fe:00 9966853 /usr/lib/libnss_compat-2.25.so
7f2acb3f8000-7f2acb5f7000 ---p 00007000 fe:00 9966853 /usr/lib/libnss_compat-2.25.so
7f2acb5f7000-7f2acb5f8000 r--p 00006000 fe:00 9966853 /usr/lib/libnss_compat-2.25.so
7f2acb5f8000-7f2acb5f9000 rw-p 00007000 fe:00 9966853 /usr/lib/libnss_compat-2.25.so
7f2acb5f9000-7f2acb5fe000 r-xp 00000000 fe:00 9968910 /usr/lib/libnss_dns-2.25.so
7f2acb5fe000-7f2acb7fd000 ---p 00005000 fe:00 9968910 /usr/lib/libnss_dns-2.25.so
7f2acb7fd000-7f2acb7fe000 r--p 00004000 fe:00 9968910 /usr/lib/libnss_dns-2.25.so
7f2acb7fe000-7f2acb7ff000 rw-p 00005000 fe:00 9968910 /usr/lib/libnss_dns-2.25.so
7f2acb7ff000-7f2acb800000 ---p 00000000 00:00 0
7f2acb800000-7f2acc000000 rw-p 00000000 00:00 0
7f2acc000000-7f2acc022000 rw-p 00000000 00:00 0
7f2acc022000-7f2ad0000000 ---p 00000000 00:00 0
7f2ad0000000-7f2ad0021000 rw-p 00000000 00:00 0
7f2ad0021000-7f2ad4000000 ---p 00000000 00:00 0
7f2ad4000000-7f2ad4021000 rw-p 00000000 00:00 0
7f2ad4021000-7f2ad8000000 ---p 00000000 00:00 0
 
@GrandMasterDash As I thought - some problem with graphic libs.

Have you tried to follow the suggestion and execute the command?:

gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache: No such file or directory
Without having access to the machine and more important - without knowledge about Manjaro linux at all, I will probably not be able to help you, but you could try to reinstall gtk-pixbuf by issuing command:

sudo apt-get install --reinstall gdk-pixbuf2.0-0

..or with its equivalent for Manajaro linux.

DMT is tested on Debian/Ubuntu.
 
Sorry, it seems too flaky, makes me nervous to use as it is.

I reinstalled gdk-pixbuf2 (2.36.8-2) and it worked, but only once. After that, back to the same problem. I also tried rebooting.

I saw you're using a non-standard file picker. Perhaps a future version can use a different file picker?

I also saw this message

Gtk-Message: Failed to load module "canberra-gtk-module"

(DashMasternodeTool-0.9.6:5218): Gtk-WARNING **: Theme parsing error: gtk.css:17:21: '-gtk-outline-radius' is not a valid property name

That's a sound module? It's already installed (and reinstalled).

I don't know what to say, all my other apps are working just fine.
 
@GrandMasterDash
I think I'm using quite standard QFileDialog class of the QT library. Please note that as I mentioned earlier this project is based on QT library and there is no easy way to influence how the library translates its API calls to various OS subsystems. Probably not all Linux distributions are supported correctly. Other applications, not based on QT library or not using QFileDialog may work correctly.

In the next version (I'm planning to release it today) I've implemented a workaroud - this version allows to manually (keyboard) enter the path to the masternode.conf. Before that, you'll need to check the "Don't use file dialogs" option in the configuration window. A solution not very elegant, but in these circumstances, my options are quite limited.
 
New version (0.9.7) of DashMasternodeTool available with some minor changes:
  • Sending funds from any address controlled by a hardware wallet (https://github.com/Bertrand256/dash-masternode-tool#transferring-of-masternode-earnings). This is a temporary and very basic solution, based on a bip32 path as an input. Future (target) solution will have a full BIP32 tree explorer.
  • Control of not matured coins (<100 confirmations) when performing funds-transfer.
  • Message box with a transaction ID, shown after successful transfer of the funds, now allows to copy a text - this was not possible on windows before. Additionally, TXID is shown as a hyperlink to a Dash block explorer.
  • Fixes of some issues with networking and connection to hardware wallets.
  • Access to the app's log file from the Tools button.
Executables:
Mac: https://github.com/Bertrand256/dash...nload/v0.9.7/DashMasternodeTool_0.9.7.mac.zip
Win64: https://github.com/Bertrand256/dash...oad/v0.9.7/DashMasternodeTool_0.9.7.win64.zip
Win32: https://github.com/Bertrand256/dash...oad/v0.9.7/DashMasternodeTool_0.9.7.win32.zip
Linux: https://github.com/Bertrand256/dash.../v0.9.7/DashMasternodeTool_0.9.7.linux.tar.gz

Major changes are underway.
 
Back
Top