Proposal “Dash-Bitcoin-improvement-protocols“ (Completed)Back
| Title: | Proposal : Dash/Bitcoin improvement protocols |
| Owner: | quantumexplorer |
| One-time payment: | 120 DASH (3579 USD) |
| Completed payments: | 1 totaling in 120 DASH (0 month remaining) |
| Payment start/end: | 2017-03-27 / 2017-04-26 (added on 2017-03-29) |
| Votes: | 645 Yes / 0 No / 9 Abstain |
Proposal description
This is a cross post from the Dash Forum.
This proposal is for Developer Documentation.
It's come to my attention that we seem to lack a repository detailing the implementation and modifications of the various bips (bitcoin improvement protocols). Even though this was fine when you have a small dev group we have started to grow to such a size where lack of this is no longer feasible.
Detailed documentation on the bips are very important for 3rd party wallet and services that will later integrate into the network. Having a central place where these bips are well documented should prove to be a huge time saver for core and non-core devs.
As an example when building the iOS wallet any feature even slightly changed from bitcoin I needed to reverse engineer from C code. 3rd party services have been doing the same up till now, or asking on the dev slack. This takes a lot of time away from other people.
The original bitcoin bips are located at https://github.com/bitcoin/bips
This proposal is to set a bounty for a fork and update on the documentation of these bips as well as a status report on each bip (completed/abandoned/partially supported) and if we don't support it, should we? There are ~100 bips, so this could take some time. I estimate about 2/3 months.
Roles :
My role will be to find people to carry out this task, manage, and help them. So far I have 2 of my software dev friends that might be interested, but are awaiting the result of this proposal and explicit terms from me to move forward to anything concrete.
[EDIT] I forgot that many of you guys don't know me. I've been contributing to DASH since early 2015 and was part of core till mid 2016 (At which time I had to leave for personal reasons). I initially wrote the iOS client (that was rejected by apple) and later contributed on various other projects. Here are some: https://github.com/dashpay/x11-hash-js https://github.com/dashpay/dark-gravity-wave-js
And most currently the iOS wallet : https://github.com/QuantumExplorer/dashwallet/tree/refresh
Costs :
I am requesting an initial 115 DASH + 5 DASH for reimbursement of proposal. I vow 100% transparency with funds. I also will make sure that no contractor will receive disproportionately more funds that a member of the core team for an equal time worked. I see a lot of proposals asking for very high amounts that would give exterior devs multiple times more money than core. I am very opposed to this.
In the case we run out of funds I will make a new proposal, but by then a sizable amount of work will already be done that should speak for itself.
In the unlikely case we have too many funds, extra funds will go to other developer documentation projects to help future Dash software Devs or will be sent back to Dash core if no such projects exist.
If you have any additional questions, please post them in the Dash Forum and tag @quantumexplorer in your message to ensure I see your post.
This proposal is for Developer Documentation.
It's come to my attention that we seem to lack a repository detailing the implementation and modifications of the various bips (bitcoin improvement protocols). Even though this was fine when you have a small dev group we have started to grow to such a size where lack of this is no longer feasible.
Detailed documentation on the bips are very important for 3rd party wallet and services that will later integrate into the network. Having a central place where these bips are well documented should prove to be a huge time saver for core and non-core devs.
As an example when building the iOS wallet any feature even slightly changed from bitcoin I needed to reverse engineer from C code. 3rd party services have been doing the same up till now, or asking on the dev slack. This takes a lot of time away from other people.
The original bitcoin bips are located at https://github.com/bitcoin/bips
This proposal is to set a bounty for a fork and update on the documentation of these bips as well as a status report on each bip (completed/abandoned/partially supported) and if we don't support it, should we? There are ~100 bips, so this could take some time. I estimate about 2/3 months.
Roles :
My role will be to find people to carry out this task, manage, and help them. So far I have 2 of my software dev friends that might be interested, but are awaiting the result of this proposal and explicit terms from me to move forward to anything concrete.
[EDIT] I forgot that many of you guys don't know me. I've been contributing to DASH since early 2015 and was part of core till mid 2016 (At which time I had to leave for personal reasons). I initially wrote the iOS client (that was rejected by apple) and later contributed on various other projects. Here are some: https://github.com/dashpay/x11-hash-js https://github.com/dashpay/dark-gravity-wave-js
And most currently the iOS wallet : https://github.com/QuantumExplorer/dashwallet/tree/refresh
Costs :
I am requesting an initial 115 DASH + 5 DASH for reimbursement of proposal. I vow 100% transparency with funds. I also will make sure that no contractor will receive disproportionately more funds that a member of the core team for an equal time worked. I see a lot of proposals asking for very high amounts that would give exterior devs multiple times more money than core. I am very opposed to this.
In the case we run out of funds I will make a new proposal, but by then a sizable amount of work will already be done that should speak for itself.
In the unlikely case we have too many funds, extra funds will go to other developer documentation projects to help future Dash software Devs or will be sent back to Dash core if no such projects exist.
If you have any additional questions, please post them in the Dash Forum and tag @quantumexplorer in your message to ensure I see your post.
Show full description ...
Discussion: Should we fund this proposal?
Submit comment
|
No comments so far?
Be the first to start the discussion! |
Many MN owners don’t realize that the deadline to vote is approximately 3 days before the superblock occurs (1,662 blocks, to be exact). So I’ve added a little reminder to the top of dashvotetracker.com: @ericsammons