Dash Budget Proposal for April 2016

The next budget payment will be block number 448632, approximately 12:00 PM UTC on Wednesday, April 6.

As Dash has grown so rapidly, we have had to make some changes to the way we operate. One of the changes we made was to the way our budget system is used and for what purpose. To date, the core team has never initiated any program to pay individual team members for outstanding work (except for a symbolic budget to thank the core team). The budget system is mainly used to reimburse actual expenses, such as airfare, conference fees, legal fees, and other actual expenses incurred.

While the budget system is amazing, there are still some problems when we use it. First, when team members pay for things to take advantage of Dash development opportunities, such as buying domains or attending conferences, they run the risk of not being covered by the Dash budget, or other proposals may receive more votes. Second, symbolic temporary payments are obviously more suitable for volunteers, but as the full-time development team expands, we need to provide salary payments if we want to make rapid progress.

Our next phase of growth will be rapid, paid development, cross-domain, and multi-tasking. This will keep the project moving at full speed, and when we are about to start, please keep your hat or it may be blown away.

Contract Requirements

Between now and the release of version 12.1, we will stop submitting additional multi-month contracts in the budgeting system. Prior to version 12.1, our budgeting system had poor support for multi-month proposals. We first encountered this issue a few months ago, and now we are experiencing the same situation again. One of the multi-month proposals was kicked out of the system, and payment was interrupted.

Once version 12.1 is released, we will no longer encounter this issue and contract budgets will be prioritized in the payment queue.

Dash Foundation Priorities

The Dash Foundation will rank existing proposals for the Dash economy early this month. The core team has invested a great deal of effort in developing a roadmap that provides the highest probability of success in the next few years, but we also need to pay more attention to where the funds are used. In our judgment, it is best to focus on R&D and infrastructure rather than advertising. We intend to immediately shift all advertising funds in the budget system to infrastructure construction.

• Dash Core Maintenance (synchronization with existing code)

• Dash Evolution Development

• Other core architectures (servers, etc.)

• Fiat-Dash exchange channels (Lamasu ATMs, local exchanges, etc.)

• Other products (debit cards, etc.)

We are very proud of the significant progress we have made in 2016, which has surpassed our previously formulated strategies, and the market has undoubtedly recognized our performance and prospects. Masternode holders are advised to vote in the order of priority of the current development plan, and of course they can vote according to their own wishes. We very much hope that we have earned your full trust.

Version 12.1 Update

We are already accelerating towards version 12.1 and will soon be completing the setting of contract-based budgets. These contracts are plans that span a 3-12 month payment cycle, which are set to be paid first and cannot be changed during the payment cycle. These settings are reached through network voting. Changes to these settings are like variables in the decentralized network, and we can use this mechanism to flexibly change network properties, such as the per-kilobyte transmission fee.
So when we deploy version 12.1 and manually add budgets in, the budget system will be “reset.” This will be a great moment to reposition ourselves for the next phase of our journey.

Previous projects:

Core Team Budget - 1176 Dash (in progress)

Public Promotion - 2156 Dash (ongoing)

Acquisition of Dash.org domain - 2100 Dash (missing one expense - see below)

Mixed currency liquidity support - 140 Dash (5th out of 12)

Dash Lamassu ATM Integration - 610 Dash (4th out of 12 payments)

New core team planned projects:

Light wallet server maintenance contract
https://www.dashwhale.org/p/electrum-maintainence

Lightweight client software allows users to access the network without downloading the entire blockchain, but this requires hosting services. We don't have very powerful equipment at the moment, and the infrastructure needs to be heavily redundant to ensure security. We have reached an agreement with Rob Nelson of mazaclub, who will maintain the other 3 devices with the latest software to keep our network running at high speed for 45.80 Dash per month.

Evolution version description
https://www.dashwhale.org/p/evo-specifications
To help the platform grow quickly, we have split the development team into two groups. I will continue to lead the core group. The second group will focus on the evolutionary version and will be led by Andy Freer, a talented engineer from the UK who is dedicated to the project. We have drafted an agreement that Andy will put aside other projects to spend more time helping the platform grow, and in return we will pay him 150 Dash per month as compensation. This is obviously a very low salary for a top engineer, and we are very grateful that Andy can devote himself to the project under these conditions.

This agreement is only a temporary solution to allow Evolution to continue to develop, it will be valid for 3 months. Once version 12.1 has the appropriate contract capabilities, we will move Andy and other network contracts to the new budget system project.

Dash.org - December Fee Reset

The acquisition of Dash.org was pre-approved late last year. It included 4 months of fees at 2,100 Dash per month. Unfortunately, something went wrong with the December budget, which prevented the finalization of all the budget. Therefore, the 2,100 Dash that was supposed to be allocated to the beginning of December was not allocated. This proposal would correct the missing fees. However, there is not much room in the budget for this month, so we are going to spread the over-budgeted fees over the next 3 months.

Acquisition of Dashtalk

Dashitalk.org has become a valuable resource for the Dash community, containing a wealth of history, work, creativity, and ideas. But Dashtalk was founded by a community member at their own expense. Because the core team cannot manage the site, we rely on its owners to fix problems when outages, license expiration, or other issues occur. If you log in to the forum frequently to access resources, you will have noticed that it has been out of service many times recently. As the database continues to grow and we rely on it, the value of the Dashtalk forum will only increase, so we must control it.

We are pleased to inform you that the core team has negotiated the acquisition of the Dashtalk project, retained the forum's historical database, and is currently in the process of transferring the management of the entire site, while software updates are also being carried out. This is really great news for the community, and from now on we can maintain the entire site ourselves at a reasonable cost.

Non-core team planned projects:

https://www.dashwhale.org/p/dash-debit-card
https://www.dashwhale.org/p/dashpay-woocommerce
https://www.dashwhale.org/p/ROKOS-permanent-add
https://www.dashwhale.org/p/DashTrader
https://www.dashwhale.org/p/DashWorld-v.2
https://www.dashwhale.org/p/Alex-ru-Promotion-1
https://www.dashwhale.org/p/Proof_of_Labour

The full budget schedule (in order of current vote ranking):

Note: The USD exchange rate for new budgets and core team budgets older than 12 months ending March 30, 2016 is set at $6.96. The exchange rate for existing recurring budgets uses the exchange rate at the time of creation/approval. The exchange rate risk only affects the applicants of these budget proposals, not the network.