bigrcanada said: Trust me...I understand the pickle our team is in. In the end there needs to be "some" trust in the team. That is why I'm voting Yes. Its in all our best interests. Thanks for the hard work team. Click to expand...

Vote for this proposal even with the business name omitted temporarily (and as several people have said we need a way to be able to do this in future or it makes us less competitive) Offer to contribute independently or as part of our team - we have invested a few weeks in this already internally, if anyone in the community wants to help or feels synergy with this kind of initiative, email me [email protected] or another team member and help us, if you work within the group that has formed of like-minded people focused on growing Dash adoption, you can easily find out this kind of information, and it's very easy to do, you just need to come and contribute. Help us promote this when it is launched - posting on social media, youtube, explaining the value to people and spreading the word. Use the service when it's launched!!! success of this integration won't be the just the implementation, it will be use of the service and that means traffic / subscriptions. This one is something i think is really useful and already moved over my existing provider. When it comes out, please help us drive users, friends, colleagues, businesses to adopt this and pay in Dash. That helps both parties to be able to grow together

Yes exactly. This ties into the whole can a fully-open/ decentralized organization compete with centralized ones.In a commercial market that's post-bitcoin and saturated with centralized / decentralized alternatives, we need to be proactive to gain adoption and grow the Dash ecosystem by forming relationships with the best/largest services in the market we are targeting to encourage and help them to adopt Dash (especially before Evolution makes this easy for all parties).When making agreements with centralized parties they will often have requirements where they don't want every last detail to be 'open source', ranging from info that's part of the agreement/setup process through to code that might exist within their proprietary platform through to releasing information at the right time / in the right stages as part of the promotions process to ensure maximum impact / uptake with information that is released.It's therefore unrealistic to demand that every detail of every action/relationship/investment is exposed if we are serious about mainstream adoption. I think if information is permanently concealed from the wider community that is against the principles of an open-source decentralized organization like Dash and I would oppose it. But when it's a temporary measure to try to help a fledgling relationship incubate and grow and the proposer has a track record of delivery and something like just the business name / sector is omitted as in this case, I don't see this is a reason to turn down gaining new access to a base of over 1 million internet users as that should really be the kind of thing people in Dash at this stage are striving for every day, because they are in every other tech startup that is serious about what they are doing (but at the same time I understand why info being held is unusual and not something that's really happened before and some people might be against it).I would go further and say we need to improve the governance system to codify this, for example have 'grey' projects that allowed certain information to be concealed for a limited time until the work/actions/relationships within the proposal are launched/formed/ready for public consumption. I've heard it voiced before and I'm not sure how that would be done and it would need to be sound with our open-source principles, but I think it would give us an advantage in the global payments market the same as it gives centralized companies who launch new products / form strategic relationships and to compete with them we need a way to do that to.In this particular case, everything will be open-source, except for maybe some code within the merchant's PHP server behind their API to us, which is a small job we would fund but I don't expect we would gain/need access to the exact implementation.I have already written ~20 pages of documentation for that over 3 revisions with the merchant and we've had calls / on-site meetings with them too, because we really want to setup a process that makes their service better and delivers more value to Dash users (which I strongly believe it will), and secondly this ties into Evolution because one of the main objectives is to make Dash friendly to Merchants and not just users and this is a 'real-world' case of a business with a large user base so this process is a great learning experience for us to learn their processes, needs and what they really want out of a payment solution that we can take to a much larger audience all in an open-source way.I would urge all network operators to:So please support this proposal, if we can get 5 of these in the next 12 months before Evolution, that means 5 million users see "Dash (Digital Cash)" as a payment option when they subscribe / buy and a lot of those users will come and check us out, and once Evolution is live, we don't have to be so proactive, the system itself will promote and make this easier.This is exactly the kind of thing a young tech project like Dash aiming for a mainstream audience should be doing if we want to actually reach that audience, therefore I urge everyone to support this proposal.Thank you for your support!