Proposal “dash-masternode-tool-continuation-3“ (Active)Back

Title:DashMasternodeTool - February-March 2019
One-time payment: 183 DASH (16529 USD)
Completed payments: no payments occurred yet (1 month remaining)
Payment start/end: 2019-03-17 / 2019-04-16 (added on 2019-03-08)
Final voting deadline: in 10 days
Votes: 326 Yes / 43 No / 1 Abstain
Will be funded: No. This proposal needs additional 190 Yes votes to become funded.
Manually vote on this proposal (DashCore - Tools - Debugconsole):
gobject vote-many 17668629fc5eaa230b04d72e4ad75e013b6eb2710e5addf074a79d7881d1c1d9 funding yes

Please login or create a new DashCentral account for comfortable one button voting!

Proposal description

This proposal concerns the continuation of the development of Dash Masternode Tool (DMT) in the period February-March 2019.

DashMasternodeTool is an application whose purpose is to help MNOs perform certain important operations related to Dash masternodes if their collateral is controlled by Trezor, KeepKey or Ledger Nano S hardware wallets. The most important of these operations are: activating the masternode in the network, status monitoring and transferring payouts without "touching" the collateal.

This proposal covers work done in the last two months, i.e. in February and March 2019. In my previous proposal, I explained the reasons why I first do the work and then I ask for funding.

The scope
In the period covered by this proposal, the distribution of my involvement was as follows:
- implementation of changes in DMT: 65% of the time
- implementation of the code in the server part required by some DMT features: 10% of the time
- user support: 25% of the time

Activities related to DMT:
- improvements of the Deterministic Masternode Migration wizard
- improvements of the DMT wallet feature, including support for handling of special transactions (DIP2) by hardware wallets

Link to the last release of the application:

Work to be done in the near future
After the recent probles of the Trezor online wallet, that were related to not (yet) supported DIP2 transactions, some people use DMT wallet not only to send masternode earnings, but also for general payments. This results in high expectations regarding the quality of this functionality. On the other hand, the DMT wallet feature is still far from being perfect, so I would like to devote the nearest available time to make further improvements in this area.

Not everything I promised in the past has been delivered. The dynamics of changes in this environment is so great that in practice, I devote more than 50% of my time to do tasks that were not taken into account during the planning. I am therefore forced to postpone the implementation of some promised features, which is quite uncomfortable for me, but necessary. Anyway, I remember all of them and will try to  implement them whenever possible.

- Compensation: 6500$ / month
- Dash price (10% margin for volatility): 73 $/Dash
- Months: 2
- Proposal cost reimbursement: 5 Dash

Amout: 6500 * 2 / 73 + 5 = 183 Dash
Cycles: 1

If the Dash price turns out to be higher than my estimates, I will expand the scope of the proposal for an additional time. If it is lower, the scope remains unchanged.

Show full description ...

Discussion: Should we fund this proposal?

Submit comment
1 point,20 hours ago
I don't doubt the importance of DMT in the Dash ecosystem but I have some questions regarding spending resources on developing the wallet function of DMT, which seems to be a significant part of the development work of this proposal.

My concern is that, Dash treasury funds are limited thus funding the development of DMT will probably come at the cost of efforts in for example Venezuela. So why would Dash fund the improvement of wallet features in DMT. Is it necessary? Will it have additional features compared to other Dash wallets? Could users also use one of the alternative wallets that are already out there, to achieve the same results?
0 points,17 hours ago
Thanks for the legitimate questions.

Actually, most of the work covered by this proposal concerns not the wallet itself, but the support for registering DIP3 masternodes. As for the wallet, the three major hardware wallet manufacturers have so far not implemented Dash special transactions support (DIP2) either in their client libraries or in their official client apps. As a result, you can not make Dash transactions if there are DIP2 outputs among your account UTXOs, which are, for example, mn earnings received after Feb 27. (Trezor's online wallet disconects when he comes across such a transaction.) DMT wallet has a workaround for this, which will be quite important for some people before the manufacturers fix it on their part.
0 points,12 hours ago
@Betrand256 are you the only person that is working on this project? Have you contracted any 3rd party independent bug and security testing service to ensure that the software does not have any security risks or issues. If just one developer is working on the code it is a good idea to get it independently tested to ensure security is maintained, especially with something as important as software that is involved with administering the MN collateral. We can't afford for there to be any unexpected security issues with the DMT tool.
1 point,3 days ago
The DMT had several bugs from the 13.x upgrade, one of which almost sunk two excellent proposals, all of this could have been avoided if the proper testing was done by the developer, which it was not. DMT raises more support issues than it resolves and MNOs need give it a level of trust because it stores some of your private keys. I tried to review the code and could not make heads or tails of it. So, I don't use DMT and would not recommend anyone to use it.
0 points,2 days ago
The main purpose of DMT is to allow masternode start if the collateral is controlled by a hardware wallet and (unfortunately) there is no other viable option to achieve this. Every now and then we are witnessing collareal thefts because of keeping them in a hot wallet on a PC, so discouraging people to use hardware wallets for this purpose isn't really reasonable.

Regarding the issues related to some secondary features, it is often the case that the error message that the user sees is the result of an error in the external module which DMT uses (e.g., hw client library) and a DMT fix is actually a workaround to allow this to work. You start to be aware of such nuances only when you deal with them directly.

Does this mean that DMT is perfect? Absolutely not. There is a lot of code, especially from the origins of the project, which is illegible. It also has bugs, which is nothing unusual especially for apps being intensively developed, but most errors are fixed quickly.
2 points,4 days ago
This is a pretty expensive proposal during this bearmarket, I would prefer masternode owners did the manual work instead if this is the ask for it.
0 points,3 days ago
It's hard to disagree, but there is also a flip side of the coin. Seeing how many people may have major problems with manual DMN registration process, which would certainly delay the adoption rate but in extreme cases could cause costly mistakes, I decided to support this process on my part. However, it required my 100-percent involvement during the course of several months, but to make it possible, I had to apply for funding. The work has been done and seeing to how many people my solution helped to complete this process quickly and easily, I can say that it completed with success. Certainly it would not be possible with my "after hours" involvement.

As supporting of DML rollout was most important task from today's perspective and there are no other similar challanges on the horizon, it's quite natural to decide that this proposal would be my last one regarding DMT, unless other unknown factors appear or the budget situation improves substancially. I'm going to switch to work in a "voluntary/after hours" mode, where I will be providing as much support as possible in such a situation.
0 points,19 hours ago
Thank you for you're honest reply
1 point,6 days ago
Thanks for quick DIP3 Ledger hotfix after not being able to collect MN payouts! Voting yes.
0 points,3 days ago
Thank you for your support.
2 points,8 days ago
easy absolute YES. The DMT needs to evolve with the Dash ecosystem.
0 points,3 days ago
Thank you.
2 points,9 days ago
Easy yes from me. I use the DMT and its an essential part of the dash ecosystem. As dash evolves the dmt needs work, everyone here has to be on board with it.
0 points,3 days ago
Thank you!