• 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

@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

Knipsel.JPG


Discord :

Knipsel.JPG


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.
 
Last edited:
@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.
 
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.
 
Last edited:
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.
 
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.
 
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.
 
@Bertrand256 We have the following issue with Platform withdrawals, when a Ledger address is registered as payout address :

Knipsel.JPG

Source : https://discord.com/channels/484546513507188745/496953691203698703/1304329274441859083
(miha was direct messaging with an imposter having the same name as you, so it became a bit messy on Discord)

So the issue at hand : Platform Withdrawals arrive in the Ledger wallet address, but can not be send out. When a Ledger address is set as payout address by an Evonode operator.

On the other hand i can personally confirm there is no problem with a Dash Core wallet address set as payout address --> receiving the Platform withdrawal in the Dash Core wallet --> through Dash Core sending it to a Ledger address --> through DMT manually sending it from Ledger address to an exchange. That works fine.

Also this :

Knipsel.JPG


and this : https://github.com/dashpay/dips/blob/master/dip-0027.md (to perhaps refresh your memory, section Asset Unlocking)

Can you please look into it, thank you.
 
Last edited:
@Bertrand256 We have the following issue with Platform withdrawals, when a Ledger address is registered as payout address :


Source : https://discord.com/channels/484546513507188745/496953691203698703/1304329274441859083
(miha was direct messaging with an imposter having the same name as you, so it became a bit messy on Discord)
.......
and this : https://github.com/dashpay/dips/blob/master/dip-0027.md (to perhaps refresh your memory, section Asset Unlocking)

Can you please look into it, thank you.
I've posted some comments on Discord.

I will look at it today, although I can there may be a small problem with it, because I do not have such evo-MN earning transaction (i.e. coinbase UTXO) available on mainnet wallet and Dash testnet isn't supported by Ledger.
 
@Bertrand256 Any progress update on detecting above issue on Trezor testnet ? I understand Ledger will be more difficult to test (no testnet).

I was thinking that maybe if / when a solution is found for Trezor hardware wallet, users with dash stuck in their Ledger hardware wallet could perhaps import the seed phrase of their Ledger wallet into a newly bought Trezor hardware wallet (cheapest one, with Dash support --> Trezor Model One?) and get their stuck dash out that way. Depends i guess how much dash is trapped, to consider this solution. And whether a seed phrase can even be imported that way, between Ledger and Trezor hardware wallets. Personally i have like 24 Dash received through Platform withdrawals trapped on my Ledger wallet, so i would not mind buying a €35 Trezor hardware wallet to free them.
 
Last edited:
Someone correct me if I'm wrong but AFAIK, the seed on Ledger and Trezor are both BIP39, so I don't think that is a problem.. However, it is a problem if, for example, a seed is deliberately geographically widespread and manually entering a seed is itself a potential security risk. Thanks Trezor, really appreciate your un-dedication to dash.

But yeah, am curious what options people are considering as their new home for long term storage.
 
Someone correct me if I'm wrong but AFAIK, the seed on Ledger and Trezor are both BIP39, so I don't think that is a problem.. However, it is a problem if, for example, a seed is deliberately geographically widespread and manually entering a seed is itself a potential security risk. Thanks Trezor, really appreciate your un-dedication to dash.

But yeah, am curious what options people are considering as their new home for long term storage.
ledger
 
@Bertrand256 We got some additional information from Splawik that Trezor hardware wallets are not affected when using DMT. Only when using the Trezor Desktop Suite are they affected (Transaction signing error: Unsupported Dash transaction type).

Since both Ledger & Trezor use BIP-39 seed phrases, i think i will just order a Trezor One, import my seed phrase and specify
the specific derivation path for Dash in Trezor for the Ledger account, where i received that stuck Dash.
And then use DMT to get that stuck Dash out.

So i don't think there is a need to further test DMT on Trezor wallets on testnet to detect any issues. You can just focus on the Ledger issue (byte array index out of range).
 
Last edited:
@Bertrand256 We got some additional information from Splawik that Trezor hardware wallets are not affected when using DMT. Only when using the Trezor Desktop Suite are they affected (Transaction signing error: Unsupported Dash transaction type).

So i don't think there is a need to further test DMT on Trezor wallets on testnet to detect any issues. You can just focus on the Ledger issue (byte array index out of range).
Thanks for the feedback. Recently, I was beginning to wonder if there was a difference between the behavior of transactions on testnet and mainnet, since I was unable to reproduce the problems on testnet.
 
I can confirm buying a Trezor One (directly from Trezor.io), recovering (Advanced Recovery) the Trezor One with the Ledger seed phrase and then using it with DMT got me that stuck dash out. I am using it as a one-time solution for my issue, as support for Dash will come to an end on Trezor hardware wallets somewhere next year.
 
Last edited:
I can confirm buying a Trezor One (directly from Trezor.io), recovering (Advanced Recovery) the Trezor One with the Ledger seed phrase and then using it with DMT got me that stuck dash out. I am using it as a one-time solution for my issue, as support for Dash will come to an end on Trezor hardware wallets somewhere next year.
I think Trezor opinion regarding the cancellation of Dash support may change if Dash shows development and price growth

most likely, the decision related to the cancellation of support for dash is related solely to an attempt to reduce development costs... and if there is interest in the dash coin, then they will have no choice
 
Back
Top