Proposal “flagship-merchant1“ (Closed)Back
| Title: | Integration With A Flagship Merchant |
| Owner: | babygiraffe |
| One-time payment: | 604 DASH (18871 USD) |
| Completed payments: | 1 totaling in 604 DASH (0 month remaining) |
| Payment start/end: | 2016-07-06 / 2016-08-20 (added on 2016-06-18) |
| Final voting deadline: | in passed |
| Votes: | 1036 Yes / 31 No / 0 Abstain |
| External information: | www.dashwhale.org/p/flagship-merchant1 |
Proposal description
This is a cross-post from Dash Forum
What is this proposal about?
One of our strategic priorities for 2016 is expanding merchant acceptance to give users the opportunity to spend Dash directly, targeting high-value use cases that leverage Dash’s unique features. We are pleased to announce that we are moving forward with implementation at a substantial merchant. An official press release will be coming soon, so I can only provide limited background.
Why should I vote for this proposal?
The merchant is a category-leading privacy-centric service with over one million users. Given the privacy-focused nature of their user base, the synergies with Dash are obvious. Currently, users must make payments using non-private methods. By adding Dash, users will now be able to enjoy full privacy across their entire experience, along with the speed of InstantSend payments (which will be supported as well). It also exposes Dash to a set of customers predisposed to placing a high-value on privacy.
The merchant is a champion of Dash and its many consumer benefits, and will represent what we consider to be a flagship client for our network. As such, we intend to deliver a superior integration to anything the client could have received with Bitcoin.
In addition, this integration will add real-world merchant integration experience to our team, which is already proving extremely valuable to inform the design of Evolution to make it even more merchant-friendly.
What resources are needed?
Rather than using a 3rd party payment processor, we will create a custom payment full-node the client can host internally accessed via a REST API to enable InstantSend payments and additional features they're requesting, to enable full privacy and decentralized payment processing for the client. Secondly, our solution will tightly integrate with the client’s own payments process for a seamless and enjoyable user experience.
This solution will require additional development support. Andy Freer is leading the team responsible. To complete the work, we will need several resources including a NodeJS developer to build the payment node and API. We will also need an HTML / PHP developer to integrate their systems. Members from the Evolution team will also help with the work under the existing core team budget.
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 integration opportunities
What is this proposal about?
One of our strategic priorities for 2016 is expanding merchant acceptance to give users the opportunity to spend Dash directly, targeting high-value use cases that leverage Dash’s unique features. We are pleased to announce that we are moving forward with implementation at a substantial merchant. An official press release will be coming soon, so I can only provide limited background.
Why should I vote for this proposal?
The merchant is a category-leading privacy-centric service with over one million users. Given the privacy-focused nature of their user base, the synergies with Dash are obvious. Currently, users must make payments using non-private methods. By adding Dash, users will now be able to enjoy full privacy across their entire experience, along with the speed of InstantSend payments (which will be supported as well). It also exposes Dash to a set of customers predisposed to placing a high-value on privacy.
The merchant is a champion of Dash and its many consumer benefits, and will represent what we consider to be a flagship client for our network. As such, we intend to deliver a superior integration to anything the client could have received with Bitcoin.
In addition, this integration will add real-world merchant integration experience to our team, which is already proving extremely valuable to inform the design of Evolution to make it even more merchant-friendly.
What resources are needed?
Rather than using a 3rd party payment processor, we will create a custom payment full-node the client can host internally accessed via a REST API to enable InstantSend payments and additional features they're requesting, to enable full privacy and decentralized payment processing for the client. Secondly, our solution will tightly integrate with the client’s own payments process for a seamless and enjoyable user experience.
This solution will require additional development support. Andy Freer is leading the team responsible. To complete the work, we will need several resources including a NodeJS developer to build the payment node and API. We will also need an HTML / PHP developer to integrate their systems. Members from the Evolution team will also help with the work under the existing core team budget.
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:
- 598.59 Dash for additional development staff ($5,000 USD @ $8.353 per Dash based on June 17th 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 integration opportunities
Show full description ...
Discussion: Should we fund this proposal?
Submit comment
|
No comments so far?
Be the first to start the discussion! |
Y.
E.
S."
-Dane Cook
If not, there's no way I think we should hand $5000 over for software only usable for one merchant.
It's also a lead-in to Evolution. The kind of things this merchant wants will be in Evolution too. It's just they won't need to run a local installation, they will connect to a decentralized API run across the MN network instead instead.
I have given some more info on the background on the Dash.org forum here: https://www.dash.org/forum/threads/proposal-integration-with-a-flagship-merchant.9200/page-2#post-97366
Thank you for your support!