Proposal “evo-X11-hash-port“ (Closed)Back
| Title: | Evolution Development - X11 Hash Port |
| Owner: | babygiraffe |
| One-time payment: | 609 DASH (17691 USD) |
| Completed payments: | 1 totaling in 609 DASH (0 month remaining) |
| Payment start/end: | 2016-07-06 / 2016-08-20 (added on 2016-06-19) |
| Final voting deadline: | in passed |
| Votes: | 1000 Yes / 0 No / 0 Abstain |
| External information: | www.dashwhale.org/p/evo-X11-hash-port |
Proposal description
This is a cross-post from Dash Forum

As we wrap up Evolution specifications, we are very pleased to announce that initial plans for the development phase of Evolution are maturing, and we are ready to begin securing additional resources that will be required for the project.
What will this proposal fund?
Andy and other core team members have been planning the next phase of activities. One of the foundational components requiring development early in the project is porting the X11 hash algorithm from C to JavaScript. The JavaScript version is needed for the core Dash JS libraries which will be used across the Evolution front-end stack.
In addition to the work the core team is performing, we estimate requiring about a month of a programmer’s time. This task will require a strong understanding of C, JavaScript, and cryptographic hashing functions. This task was selected to outsource because it represents a stand-alone effort, allowing the team to focus on the design activities while accelerating the delivery of the project.
The work is expected to begin in August and be completed in September. We estimate the total funding required beyond the capacity of the core team to be $5,000.
Requested funding is as follows for the July 6th budget cycle:
Note: Should any funding remain after the project is complete, we will reserve those funds for future Evolution development projects

As we wrap up Evolution specifications, we are very pleased to announce that initial plans for the development phase of Evolution are maturing, and we are ready to begin securing additional resources that will be required for the project.
What will this proposal fund?
Andy and other core team members have been planning the next phase of activities. One of the foundational components requiring development early in the project is porting the X11 hash algorithm from C to JavaScript. The JavaScript version is needed for the core Dash JS libraries which will be used across the Evolution front-end stack.
In addition to the work the core team is performing, we estimate requiring about a month of a programmer’s time. This task will require a strong understanding of C, JavaScript, and cryptographic hashing functions. This task was selected to outsource because it represents a stand-alone effort, allowing the team to focus on the design activities while accelerating the delivery of the project.
The work is expected to begin in August and be completed in September. We estimate the total funding required beyond the capacity of the core team to be $5,000.
Requested funding is as follows for the July 6th budget cycle:
- 604.45 Dash for additional development staff ($5,000 USD @ $8.272 per Dash based on June 18th average rate at https://bitinfocharts.com/comparison/price-dash.html)
- 5.00 Dash reimbursement for the proposal cost
Note: Should any funding remain after the project is complete, we will reserve those funds for future Evolution development projects
Show full description ...
Discussion: Should we fund this proposal?
Submit comment
|
No comments so far?
Be the first to start the discussion! |
I will vote yes nonetheless as this is going to be a central part of Evolution. Hope the quality of the result is going to match the price tag.
Personally I think the amount is low for a working JS implementation of X11.
Like nmarley said, it is a fair amount of work. There are 11 algos and probably only 2 suitable in JS at 512 bits (although if anyone finds more please let me know andy@dash.org). We also want to allocate some of this for some consultant cryptanalysis and/or bounties to find flaws to ensure it is thoroughly vetted by as many different parties as possible and once implemented we will be working/testing with it for around 6 months before it goes near any production products most likely.
Thank you