GUI tool for running Masternode with Trezor

Honestly I'm a bit surprised it doesn't work, because similar issues were reported for Trezor and just when I started looking into it, Trezor started working fine for those who reported it to me. I assumed then that some Platform update fixed the issue for Trezor and Ledger.

Well, if the problem is still relevant for Ledger, I am ready to try to work out some solution. However, for this I need to have some UTXO from withdrawal from the Platform in my wallet. I don't have an Evonode, so if someone could withdraw a small amount (like 0.01 Dash) directing it to my address (Xey2vihQkWJWPBQr6pRLMX2PRZM2YMyc86), I would have material for testing. Thanks in advance. I will of course send the same amount back.
I will do that with next epoch (20th of January, 23:00). Could take a day to get processed.
 
Last edited:
@Bertrand256 : should be in your Ledger wallet right now, no need to return it. I will test it in my Ledger wallet too (i send some to myself as well)

Update :

DMT v0.9.39
Ledger Nano X firmware 2.0.2 (avoiding updating to v2.2.3 for now)

Tried to move the Platform withdrawal from Ledger hardware wallet address to Dash Core wallet address :

Knipsel.JPG
 
Last edited by a moderator:
@Bertrand256 : should be in your Ledger wallet right now, no need to return it. I will test it in my Ledger wallet too (i send some to myself as well)
I confirm that I received the transaction (thanks) and that I was able to reproduce the issue.
For now, I can only say is that the problem stems from the Ledger Python client library. Whether a workaround will be feasible or not, I will say after an analysis (which may take a few days).
 
@Bertrand256 : should be in your Ledger wallet right now, no need to return it. I will test it in my Ledger wallet too (i send some to myself as well)

I managed to solve the problem. The reason was that the official Ledger Python library assumed that the transaction has a structure consistent with a Bitcoin transaction. For Dash, this worked until recently, when withdrawal transactions from the Platform (type 9) were introduced. As a solution, I applied a live-patch of the original library while running within DMT.

Let me know if you want to test the patch before I prepare the official release - if so, I will prepare a beta version and share it somewhere.
 
I managed to solve the problem. The reason was that the official Ledger Python library assumed that the transaction has a structure consistent with a Bitcoin transaction. For Dash, this worked until recently, when withdrawal transactions from the Platform (type 9) were introduced. As a solution, I applied a live-patch of the original library while running within DMT.

Let me know if you want to test the patch before I prepare the official release - if so, I will prepare a beta version and share it somewhere.
That is good news !!
I trust that this will fix the problem, so just go ahead with the official release.
Thank you.
 
Ok. It will take a few more days to update other libraries like Trezor, which, btw, likes to break backwards compatibility :).
We currently do not have an issue with Trezor in combination with DMT.
We just have this issue with Ledger in combination with DMT.

Not sure we should mess with Trezor library, when its working fine with DMT.
------------------------------------------------------------------------------------------------------------------------------------------------------------------
Knipsel.JPG


Knipsel.JPG

------------------------------------------------------------------------------------------------------------------------------------------------------------------
Should we not just fix the Ledger Python library and leave the rest as is ? Or are you perhaps talking about needing to recompile other libraries as well (Trezor for example) for the new DMT version, but not really needing to fix them ? I am a little bit confused about you mentioning Trezor.
 
Last edited:
Back
Top