GUI tool for running Masternode with Trezor

[AgnewPickens]

Maybe an off topic question, would a tool for searching through past votes and finding other MNs that voted the same as your own be possible? Delegating votes could be a great feature but it doesn't seem to be used much, wondering if being able to find other MNs with closely matched voting history and saying "vote the same way" would be a useful feature, either delegated or just in-app. Thanks.

@xkcd Is working on something like with his MNOWatch tool, but perhaps open a fresh discussion for this?

 

[Bertrand256]

Maybe an off topic question, would a tool for searching through past votes and finding other MNs that voted the same as your own be possible?

As the data on inactive proposals is not stored anywhere on the Dash network, creating such a feature that works independently isn't feasible. The only option is to do it within a site that stores the historic results in its database, such as DashCentral or Dash Nexus.

Delegating votes could be a great feature but

Configuring a voting delegate configuration in DMT has been possible for some time. For this, in the field "User role" you need to select only the field "Voting" and fill in all active fields.

 

[xkcd]

https://mnowatch.org/ come join the fun!
Quick primer. https://www.reddit.com/r/dashpay/comments/hs4l6m

 

[Bertrand256]

DashMasternodeTool v0.9.26-hotfix4 released
Binaries: https://github.com/Bertrand256/dash-masternode-tool/releases/tag/v0.9.26-hotfix4

Changes:

• Fixed an error occurring when signing transactions with Trezor using the latest firmware: "Required field 'amount' was not received".
• Fixed an error in the firmware update wizard for Trezor devices.

BTW, I would like to let you know, that in a separate thread I am working on my last proposal from a few months ago. Although I was hoping to finish it sooner, nevertheless it's good that the most important part (i.e. adapting to the latest versions of Qt, Trezor, Ledger, Keepkey libraries) is already completed. Now, I'm working on new features.

 

[geolibertarian]

DashMasternodeTool v0.9.26-hotfix4 released
Binaries: https://github.com/Bertrand256/dash-masternode-tool/releases/tag/v0.9.26-hotfix4

The hashes for the mac release don't match.

On the releases page, this is the hash you list:

shasum -b -a 512 DashMasternodeTool_0.9.26-hotfix4.mac.dmg
4e511269e9416515d6ebcbc9fa8b51a377f9f51b76d65252fd604614b0a76525e3de8cd4e4401ecd8af389ab5cdb4954580ccf9fb2ad064c4df5fdc14e2c0d40 *DashMasternodeTool_0.9.26-hotfix4.mac.dmg

This is what I get:

shasum -b -a 512 DashMasternodeTool_0.9.26-hotfix4.mac.dmg
1665163027d49772e2da6f830b4c5e8d834112cd1e1e941912fd7531e4e89ccb8cf247d87012cbd5ccc22f40e199ab76109c9e2cb0cbf2401526b3d7a4e6b179 *DashMasternodeTool_0.9.26-hotfix4.mac.dmg

Is it just me, or is there a mistake? Thanks.

 

[geolibertarian]

Is it just me, or is there a mistake? Thanks.

Ok weird, guess it was just me. I had tried downloading it twice and got the same wrong hash both times. Just tried it a third time and it's correct.

 

[Bertrand256]

The hashes for the mac release don't match.

Yes you are right. Due to a typo, I was re-generating the GPG message and unintentionally re-created the dmg file, which unfortunately I didn't upload to Github along with a new GPG message. A regenerated Mac dmg file, even from the same input files, gives a different binary output, hence a different hash.

Just a moment ago I have uploaded a mac dmg file with a hash matching the signature, i.e.: 4e511269e9416515d6ebcbc9fa8b51a377f9f51b76d65252fd604614b0a76525e3de8cd4e4401ecd8af389ab5cdb4954580ccf9fb2ad064c4df5fdc14e2c0d40.

Thanks for letting me know and sorry for the confusion.

 

[Bertrand256]

Ok weird, guess it was just me. I had tried downloading it twice and got the same wrong hash both times. Just tried it a third time and it's correct.

Our actions coincided in time and your last download was for the one I just published.