GUI tool for running Masternode with Trezor

[Bertrand256]

@Bertrand256
I am also having the following error on mac:
“DashMasternodeTool.app” can’t be opened because Apple cannot check it for malicious software.

Because Apple doesn't know the software, they are a little bit careful, but you can circumvent their hesitancy by the following sequence of actions:
1. open your Applications folder with finder
2. locate the DashMasternodeTool.app item
3. right click and then choose Open

This has to be done only once per any new version.

 

[kot]

I have never had this problem before. It works now - thanks for the tip Bertrand!

 

[Bertrand256]

I have never had this problem before. It works now - thanks for the tip Bertrand!

Yeah, in this regard, they (Apple and Microsoft) change the rules all the time.
Thanks for the feedback!

 

[Bertrand256]

DashMaternodeTool v0.9.34 released
Binaries: https://github.com/Bertrand256/dash-masternode-tool/releases/tag/v0.9.34

This release addresses a few issues reported after releasing v0.9.33:

• Support the old BLS scheme when showing the configuration-to-network discrepancies to avoid the "Operator public key mismatch..." warning;
• Respect the vote Signal and Weight fields when drawing the voting progress chart (proposals);
• Fixed an error that appeared when using the "Fetch MN data" feature;

 

[GrandMasterDash]

@Bertrand256 can you please give us some data on how many unique masternodes use your servers instead of doing it manually?

I suppose the logic might be, how many masternodes are still running that used DMT during setup?

 

[Bertrand256]

@Bertrand256 can you please give us some data on how many unique masternodes use your servers instead of doing it manually?

I suppose the logic might be, how many masternodes are still running that used DMT during setup?

I have no such data. Neither on the RPC nodes nor in the application itself is there any logging to identify masternodes that are created using the DMT's so called "automatic method". I think, the only way to check this would be to see what protx register transactions have been paid by the addresses of the wallets associated with these RPC nodes, but this would not show the use of the automatic method with the user's own RPC node (if that's of interest to you as well) and well, and it would require quite a lot of work to get the data. If you are interested, I can PM you wallet addresses of the public RPC nodes, so you will be able to do these verifications.

 

[splawik21]

protx register transactions

Not only those txs ^^ every single change via the MN actions, register, update pauyout, operator key, voting, service, revoke uses the fee from that address you mentioned.