Search results

A few words about the priorities, because it may not be obvious to everyone. The most important feature in the upcoming version is the support of TESTNET. Here's why: to analyze some of the issues reported and to improve some existing features, it is sometimes necessary to turn off a...

A brief update of what is being brewing as part of the next version of DMT: TESTNET support working with variuos configuration files (the open/save features) payment window: the possibility of sending only a part of an UTXO payment window: the possibility of making payment to multiple...

According to the information that I've posted while releasing v0.9.16, I've changed the two "public" RPC servers configuration (alice and luna), specifically their listen TCP port number (from 8080 to 443) and the domain name (from dash-dmt.eu to dash-masternode-tool.org). The appropriate...

For those who are interested in building DMT executables themselves, I have just published: a) documentation of the process Mac: https://github.com/Bertrand256/dash-masternode-tool/blob/master/doc/build-dmt-mac.md Windows...

Julian Hosp is very vocal when it comes to legal issues, so it's not very likely he will want to have an illegal event in the company's history, which is certainly the taking of funds and failure to comply with the obligations. The alleged "legal issues" related to PrivateSend are irrelevant...

They did not activate Dash for all users, nor did they do it for all MNOs who asked for it - I know one MNO who is still waiting for the activation from mid November, when she was told that Dash in her wallet will be activated "soon" (along the way the "Wavecrest" thing happened). Personally...

Thank you for confirming that the solution works for you.

I've published a compilation with the option I've mentioned above. For now it's published only on Keybase: https://keybase.pub/bertrand256/dash-masternode-tool/executables/0.9.17a/ In the configuration window, open the "Miescellaneous" tab and for the "KeepKey passphrase encoding" option select...

Thanks to @splawik21 (kudos to him :-) ), we managed to find the reason of the issue, which are the national characters (non-ASCII) in an passphrase. It turns out that if the password contains such characters, Keepkey uses an invalid encoding (NFC instead of NFKD) - it makes it incompatible with...

A few questions before we start digging deeper. Did you close your Keepkey client app before trying to send funds with DMT? If no, close it and try again. If yes and the error still appears, let's use another method of retrieving the dash addresses for a given bip32 path with those two...

Short answer: not possible or at least: not without extra effort. Longer answer: DMT depends on the PyQt5 library, which is not officially available for Raspbian OS. You would probably be able to compile the library from sources, though this would not be a very trivial task.

Yes, in the course of half a year, two other people reported the same error, but so far I wasn't able to find the cause nor reproduce it, however, some tests indicated conflicts with other graphics software. Do you have Steam or other game engine installed on this computer?

What's your Linux distro? Is v0.9.14 running OK on the same system?

New version of DashMasternodeTool (v0.9.16) has been released. Changelist: https://github.com/Bertrand256/dash-masternode-tool/blob/master/changelog.md#0915---2018-01-18 https://github.com/Bertrand256/dash-masternode-tool/blob/master/changelog.md#0916---2018-01-23 The most important changes...

DashMasternodeTool file is a compiled executable with python sources and interpreter inside it - you just need to execute it like a normal linux program.

I have a few other questions/suggestions: - what is your destintation address type, multisig (P2SH) or normal (P2PKH) Dash address? If you don't know this, give me the first character of your destination address. - if open, please close your web browsers that you use as an interface to...

What is the version number of your Trezor's firmware?

You probably have your mn collaterals addresses located in different bip32 paths (e.g. 44'/5'/0'/0/0 and 44'/5'/1'/0/0) and you are trying to sign its UTXOs as a one transaction. If so, the reason is a Trezor's firmware bug. I've reported it to Satoshi Labs - they said they will fix it soon, but...

Ok, added to the closest feature list.

Ok, I'll change the format in the next version or at least there will be an option for changing this on the user's level (some people prefer scientific format).