Proposal “dash-masternode-tool-infr-and-doc-update“ (Active)Back

Title:Dash Masternode Tool - infrastructure and documentation update
Owner:Bertrand256
One-time payment: 53 DASH (6817 USD)
Completed payments: no payments occurred yet (1 month remaining)
Payment start/end: 2022-01-11 / 2022-02-10 (added on 2021-12-31)
Final voting deadline: in 1 month
Votes: 449 Yes / 34 No / 0 Abstain
Will be funded: No. This proposal needs additional 24 Yes votes to become funded.
Manually vote on this proposal (DashCore - Tools - Debugconsole):
gobject vote-many b8da5043df3f06ad0a193c7a13994e57b65884f8ae6750bfa69639bcac9d7640 funding yes

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

Proposal description

This proposal is related to the Dash  Masternode Tool program (DMT for short), which I started working on in 2017, whose source code is available at https://github.com/Bertrand256/dash-masternode-tool. At the moment, the program is in the maintenance phase, that is, no new major features are added and my activities are limited to ensure its correct operation.

This proposal consists of the following parts:
1. covering the costs of renting the server infrastructure used by Dash Masternode Tool ("public" RPC nodes);
2. covering the expenses incurred for the infrastructure against the funds obtained from the last proposal for this scope (it was necessary to purchase additional storage space and pay for several additional months);
3. covering the costs of renewing the domain dash-masternode-tool.org for another year;
4. covering the costs of (planned) work related to updating the program to the latest versions of libraries (PyQt5, libusb1, trezor and others), updating the documentation to the current state of the app and server work related to moving RPC nodes to other VPS providers;

RPC nodes
The RPC nodes in question are VPS services that run dashd along with a few other software components, providing gateway to the Dash network for the app's (DMT) clients. Although the program allows users to use their own (local) RPC nodes, many of them prefer to use ready-made "public" nodes rather than install (and maintain) their own.
Each node runs three dashd instances: (a) for mainnet, (b) for testnet and (c) for development/troubleshooting, so it requires slightly more hardware resources than a regular node, i.e.: 8GB RAM, 160 GB HDD.
In the past year, I've been using one of the cheap VPS providers (OVH), but the low cost comes at the price of far from perfect stability, which results in having to spend precious time troubleshooting. Therefore, I decided to move to a slightly more expensive, but more stable platforms, such as: Digital Ocean and Linode, where the monthly cost for one VPS is: $40 + VAT.

Budget
1. VPS 2022: $40 * 2 * 12 = 960 * 1.23 (VAT) = $1180
2. VPS 2021: $120
3. Domain: $15 * 1.23 (VAT) = $18.45
4. DMT & documentation update and server work (15 MD): $4500

Total [USD]: (1180 + 120 + 18.45) * 1.32 + 4500 = 6240
Dash price [USD]: 130

Total [Dash]: 48 + 5 (proposal fee) = 53

Note: I had to add 23% VAT and 32% income tax (which I incur when exchanging Dash for FIAT) to the final price of the purchased services.

Show full description ...

Discussion: Should we fund this proposal?

Submit comment
 
2 points,8 days ago
Dash Masternode Tool has become essential in my view, as it fully supports Dash on Ledger products, where as Ledger Live (Ledger official software application to access and control Ledger products) has limitations with regards to Dash. For example Ledger Live does not support masternode payments on its Ledger hardware wallets, Dash Masternode Tool does.

Dash Masternode Tool is also a powerful tool for setting up masternodes and since this one-time payment budget request is only focused on covering the upkeep cost and in my view is essential, it will have my support.
Reply
0 points,6 days ago
Thanks for your support.
Reply
1 point,7 days ago
It is stupid putting your payment address on the hardware wallet, it should be in your QT wallet so you can mix the funds as they arrive before spending them, also some hardware wallets do not have computational power to spend masternode payments causing distress to the user when they get odd errors and cannot spend their coins. Not only that, but sometimes when the MNO tries to spend the payments, they accidently spend the 1000 Dash destroying the masternode because of no coin control on the hardware wallets! Do yourself a favour and register your payout address in a QT wallet and use the hardware wallet only for the 1000 Dash collateral.
Reply
2 points,1 day ago
You can put payout address on hw wallet and mix it with Dash Electrum later. Just my 5 duffs
Reply
0 points,18 hours ago
I think its all about choices...

You can choose to use a hardware wallet as payout address and then choose to either sent the mn payment directly to an exchange or choose to sent it to a software wallet (or Dash Electrum) first for mixing, before sending it to an exchange. Depends if people want some level of privacy on their masternode payments or settle for blockchain pseudo anonymity. Personally i don't feel a need to mix my masternode payments before sending them to my exchange.

Just like you can choose to either sent the mn payments out directly after receiving them in your hardware wallet of save them up and bundle the mn payments every few months by manually sending them to your own hardware payout address. I tried both ways, and both ways work without a problem for me on DMT (connected to a Ledger Blue).

Just my 5 duffs
Reply
3 points,10 days ago
I think this is worth supporting after considering that there are other ways to run a masternode, this is still, IMO the easiest most intuitive and that would encourage more individuals to run masternodes. This equates to more decentralization for a small price.
Reply
0 points,1 day ago
Thnaks.
Reply