Proposal “dash-masternode-tool-infrastructure“ (Completed)Back
Title: | Dash Masternode Tool - Infrastructure |
Owner: | Bertrand256 |
One-time payment: | 16 DASH (598 USD) |
Completed payments: | 1 totaling in 16 DASH (0 month remaining) |
Payment start/end: | 2019-07-17 / 2019-08-16 (added on 2019-07-13) |
Votes: | 822 Yes / 13 No / 17 Abstain |
External information: | app.dashnexus.org/proposals/dash-masternode-tool-infrastructure/overview |
Proposal description
The goal of this proposal is to provide financing for infrastructure related to Dash Masternode Tool (DMT) for the next 12 months, which has so far been covered by my own funds.
In particular this applies to:
RPC nodes.
RPC nodes referred to here are VPS servers running dashd instances along with a few other software components and the selected API functions shared to the public, which are the default gateway to the Dash network for Dash Masternode Tool. While DMT allows using your own RPC nodes, but in order to simplify the use of the program, especially for those who start dealing with it, I decided to provide dedicated RPC nodes, which I define as "public". Each node supports both mainnet and testnet, so the planned configuration is 4GB RAM. The cost is about USD 20/each/month (excluding taxes).
Some statistical information from CloudFlare regarding RPC nodes:
DMT has a GUI for a group of functions related to the registration and reconfiguration of masternodes at the blockchain level - protx calls. Using DMT you can easily overlook this, but every protx operation involves a certain (fortunately small) tx fee. Since currently none of the hardware wallets supports such transactions, DMT carries them out through "public" RPC nodes that pay the appropriate fees for the user. Therefore, it is required that in the wallet of each of such nodes there are funds allocated for this purpose. Until now, these were my private funds (of which about 3,500 protx transactions were covered), but the goal is to allocate funds from Dash Treasury: 0.3 Dash on each node.
Domain dash-masternode-tool.org
The domain is currently paid for by the end of the year, so I plan to extend its validity for the next year.
Budget:
a) USD:
VPS: 20$ * 3 * 12 = 720
Domain: 15$
Sum: 735 * 1.23 / 0.68 = 1329$
b) Dash:
Protx fees: 1 Dash
Dash/USD price: 138
Budget total: 1329 / 138 = 9.6 Dash + 1 Dash + 5 Dash (proposal fee) = 15.6
Notes:
In particular this applies to:
- "public" RPC nodes for mainnet and testnet
- the dash-masternode-tool.org domain
- funds dedicated to cover transaction fees for protx transactions carried out by the "public" RPC nodes
RPC nodes.
RPC nodes referred to here are VPS servers running dashd instances along with a few other software components and the selected API functions shared to the public, which are the default gateway to the Dash network for Dash Masternode Tool. While DMT allows using your own RPC nodes, but in order to simplify the use of the program, especially for those who start dealing with it, I decided to provide dedicated RPC nodes, which I define as "public". Each node supports both mainnet and testnet, so the planned configuration is 4GB RAM. The cost is about USD 20/each/month (excluding taxes).
Some statistical information from CloudFlare regarding RPC nodes:
- monthly number of unique users: 1500
- monthly data served: 35 GB
DMT has a GUI for a group of functions related to the registration and reconfiguration of masternodes at the blockchain level - protx calls. Using DMT you can easily overlook this, but every protx operation involves a certain (fortunately small) tx fee. Since currently none of the hardware wallets supports such transactions, DMT carries them out through "public" RPC nodes that pay the appropriate fees for the user. Therefore, it is required that in the wallet of each of such nodes there are funds allocated for this purpose. Until now, these were my private funds (of which about 3,500 protx transactions were covered), but the goal is to allocate funds from Dash Treasury: 0.3 Dash on each node.
Domain dash-masternode-tool.org
The domain is currently paid for by the end of the year, so I plan to extend its validity for the next year.
Budget:
a) USD:
VPS: 20$ * 3 * 12 = 720
Domain: 15$
Sum: 735 * 1.23 / 0.68 = 1329$
b) Dash:
Protx fees: 1 Dash
Dash/USD price: 138
Budget total: 1329 / 138 = 9.6 Dash + 1 Dash + 5 Dash (proposal fee) = 15.6
Notes:
- 1.23 multiplier: 23% VAT which is added to my purchase of services as an EU citizen
- 0.68 divider: 32% income tax, which in my case has to be paid when converting crypto to fiat
- difference of the final Dash/USD price in relation to the assumed value will be applied to the actual number of months for which services will be purchased
Show full description ...
Discussion: Should we fund this proposal?
Submit comment
No comments so far?
Be the first to start the discussion! |
Dash Masternode Tool - February-March 2019 by Bertrand256
https://beta.dashwatch.org/r/MAY19/dash-masternode-tool-continuation-3
I do wish in the future this would also be available on mobile phones through apps, meaning less dependence on windows pc / tablet / laptop (pure for conviennience).
But at the same time i do realise that will require different developer skills and experience.
Feature request: It would also be great if we could export data directly from MN hosting companies such as allnodes.com and node40.com and then import directly all congif fields in one go into the DMT tool.
The hosting companies currently provide a standard output of data that we need to manually transfer field by field to the DMT tool -it would be quicker and less prone to an error if we could simply import via CSV. It would also be in the interests of the hosting companies to work with DMT project for compatibility with DMT for import. MNOs could then simply select their hosting company in the DMT tool and provide the path to the import file and the DMT tool would import the data with a single click.
DeepBlue
Is the description of the data export format available to the public?
Remember DeepBlue that too much stuff is not good neither as it cuts out the simplicity.
There are currently checks implemented to verify if the key is in the right format etc.
Anyway I do agree that DMT is needed product which if requested by many ;)
When the Dash Tresury gets a bit more room, I will probably return to a more intensive development than just maintanance as it is now. There are certainly a lot of things that can be improved.