GUI tool for running Masternode with Trezor

[qwizzie]

@Bertrand256

Heads-up with regards to Platform credits withdrawals to dash :

https://www.dash.org/forum/index.ph...er-to-get-paid-on-platform.55016/#post-238728

Discord :

I am not sure at this point if DMT needs to have changes to make it compatible with Platform withdrawals (once enabled on Mainnet) to those Dash users who have the payout address of their Evonode registered to a hardware wallet address.

 

[Bertrand256]

@Bertrand256

I am not sure at this point if DMT needs to have changes to make it compatible with Platform withdrawals (once enabled on Mainnet) to those Dash users who have the payout address of their Evonode registered to a hardware wallet address.

At this point, I do not have sufficient knowledge of what specific operations need to be performed with the private key associated with the withdrawal address residing in hardware wallets to declare that DMT will be able to potentially (i.e., after appropriate changes) handle this situation. However, it will only be possible to analyze implementing the needed changes once the withdrawal operation is functioning on testnet, which according to xkcd, does not currently work - since not everything is documented, I need to perform some tests to see how it works in reality.

So if anyone has information that this is finally possible, please ping me, then I'll be able to delve more into the subject.

 

[splawik21]

I'm sure once it's out @thephez will let us all know.

 

[Bertrand256]

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

Changes​

• Adapting to changes introduced in Dash v21 API (what resolves issues related to wallet and transactions)
• Adapting the payment queue calculation & proposal window to the existence of Evo masternodes.

Notes [edited]​

No longer valid:

When using the "Update Payout address/Operator/Voting key" function in conjunction with public RPC nodes, you may encounter the error "-32603: failed to sign special tx". However, this is not an issue with the DMT application but rather a problem with the custom-built version of dashd, which is necessary to execute fee-based transactions on behalf of users. The issue is being addressed independently, and in the meantime, I suggest using your own Dash nodes, which are also supported by DMT.

[Edit]
For those who encountered the error "-32603: failed to sign special tx" when trying to invoke "Update Payout address/Operator key/Voting key": changes have been made at the RPC node level to ensure they function correctly with v21.

 

[dote]

Deprecated coins, trezor.

Beginning in February 2025, Trezor Suite will discontinue support for Dash, Bitcoin Gold, DigiByte, Namecoin, and Vertcoin. Users are advised to migrate their funds to alternative wallets to ensure continued access and security.

Only Trezor Model T and Trezor Model One will be affected by this change; the latest devices (Safe 3 and Safe 5) do not support the affected coins. Future hardware releases will not support these coins.

 

[splawik21]

Deprecated coins, trezor.

Beginning in February 2025, Trezor Suite will discontinue support for Dash, Bitcoin Gold, DigiByte, Namecoin, and Vertcoin. Users are advised to migrate their funds to alternative wallets to ensure continued access and security.

Only Trezor Model T and Trezor Model One will be affected by this change; the latest devices (Safe 3 and Safe 5) do not support the affected coins. Future hardware releases will not support these coins.

DCG is in talks with them, let's see what comes out from it.
Also, I will quote them here:

I want to begin with letting you know that Trezor will continue to support Dash in our firmware. This means you can still securely manage your Dash assets using third-party wallets that are compatible with Trezor.

This ^^ means that you can still keep your Dash on Trezor and access them via Dash Masternode Tool of @Bertrand256 or using Electrum Dash downloadable from GitHub and/or dash-electrum.org.

 

[GrandMasterDash]

DCG is in talks with them, let's see what comes out from it.
Also, I will quote them here:

This ^^ means that you can still keep your Dash on Trezor and access them via Dash Masternode Tool of @Bertrand256 or using Electrum Dash downloadable from GitHub and/or dash-electrum.org.

This is true but the real implications of trezor's decision is not technical. To some, this will confirm that dash is out of favor / not worthy of attention, especially when you look at the other "shitcoins" in this batch. Plus new trezor users will not be exposed to the dash brand. To entice users, dash needs to be seen at multiple locations, trezor being one of them.

This is what happens when bizdev and profitability aren't prioritized.