Each month, the ten most popular questions submitted by the Dash community at Dash Nation Discord are collected and sent to Dash Core Group for answers. The intention is to select important and well-thought out questions and filter out unpopular questions, questions that have already been answered and other noise. For January, the questions were combined with the 2018 Q4 Summary Call, and those that could not be answered there will be answered in writing in this extra-large question thread! Apologies for any errors in the automatic voice transcription. The submissions for January 2019 are as follows: Q: When will the new roadmap that was presented to us on an earlier quarterly call by Bob Carroll (CTO) as a new draft roadmap concept, be implemented on GitHub and on our official Dash forum? So we can finally start referring people to it.... Note: I understand our new roadmap will not have specific delivery dates, the calendar periods used in the draft concept (Q3 / Q4 / Q1) should be sufficient, once updated from draft. (qwizzie/PawełRzo) A (Bob): The the real question in there is when can we start referring people to a roadmap that is up-to-date, current and easily accessible. We've decided that the the best location for a roadmap is going to be our website, which will be live within the next month. That's because it's a living document that we're going to update on a regular basis, and we want people to be able to go to it. Due to the fact that it's not necessarily a community maintained document, that it's maintained by DCG, we don't feel that GitHub is actually the appropriate spot for it. So that roadmap will be retired, we'll leave it up there as historical content, and the new roadmap will be on on the website. It will take the form that Liz Robuck, our Chief Product Officer, has been putting together and using, and that we've been collaborating on over the last couple quarterly calls. So it'll look a bit more like we have today with some interactivity to it so we can drill down and find out details about features as well. Thanks. Q: In the 2018 Q3 summary call in November, Bob mentioned that there are a series of (outdated) Evolution whitepapers from 2016/2017 that have not been released, and that he would like to release them because they have historical value. I have not heard anything about this since then - is this going to happen? (TroyDash) A (Bob): As I mentioned before, this whitepaper - it's about a 60 page document - is a great artifact, it's really the original thinking that we have on the topic. It was the basis of our patent application that occurred back in 2017. We have some additional patent activity going on right now, so that whitepaper is actually intertwined with the additional patent activity. We should be through that process sometime in March, and my goal is at that point in time to actually have a "version one" of the whitepaper. The original whitepaper, obviously since not many people have seen it, was marked "version zero draft". In going through this patent process, we will be developing a "version one", but my desire is to actually publish both. I think it's important to have historical perspectives, and that is why I liked that document, however we owe it to the community to make sure that we're managing expectations correctly and putting out accurate content. We would not want it to be misleading if there were design ideas in there and our implementation varied from them. We wanted to be careful with that as well, but like I said, I like the fact that we have some history that we can present, and we intend to present both of those. Q: DCG asked for MNO's to support a $500K proposal for BitGo to integrate Dash, it's all seems to have gone quiet since it got funded. Have there been any notable integrations or developments since BitGo added Dash? If yes, what are they? A (Ryan): BitGo is a custodial service, for those that aren't familiar with it. They continue to add new services to their platform, but primarily they are used for storing larger amounts of funds in a highly secure way, typically for corporate clients. BitGo is a prerequisite for many of the exchanges that are of high priority to the network. The BitGo integration is now complete, I think it was completed around the October time frame if I recall correctly. That has enabled us to begin to pursue other opportunities. BitGo also services institutional clients, so for larger holders or investment firms that might hold Dash as part of a portfolio, such as index type of funds that we've seen pop up in the marketplace, for many of those funds it is also a prerequisite. So for various reasons it was important that we get on BitGo's platform. They're the leader in their segments of the market, and they are a dependency for us to be able to pursue a lot of these other opportunities. We are in discussions with some of their customers - I can't disclose which ones - but that has opened the door for us. Our hope is that we'll have some integrations result from it now that we're able to have these discussions. So it's very important for a variety of different reasons, and it took some time to integrate but here in the fourth quarter they did complete the integration. Q: Are there any features or functionality specifically planned for businesses in the Dashpay app or Evolution Account Management? Have businesses been asked for input or testing yet? If not when do you plan on having an Evolution alpha release to share with partners? (Mark Mason) A (Bob): We have plans for merchant features and functionality in Dashpay. What I would consider to be true business to consumer features, like order history for a customer that would be represented in a one-to-many relationship with each customer having multiple orders, however will not be in our MVP. The MVP version, like wallets today, can still accommodate merchants to work with customers, but they're doing it more on a consumer to consumer perspective, as opposed to business to consumer. It'll be a lot easier because we'll have user names in there, so follow-on releases would have merchant capabilities. We have been working with some businesses to understand what the requirements are there, and as far as alpha releases go, as soon as we have dates on that we'll publish that on the roadmap. Q: Is DCG planning on releasing an SDK or something to that effect ahead of 1.0 so that developers have time to build out dapps and integrations ahead of launch? I don't know how that might impact the timeline, but I think it would be an enormous benefit to jumpstart the dapp ecosystem. (Arthyron) A (Bob): We agree with that question and that point. We don't think that it would impact timelines to do that - it is just part of what we plan on doing. The developer community is really critical, and we do want to give them advance opportunities to work with our technology. Our first effort here is to make all of our Evolution repositories public as soon as possible, that would be this quarter, so we'll be sharing those repositories to engage the community. This helps us to improve our code quality, but also having them public is going to facilitate development activity on the new platform. Then following that, we have plans prior to MVP releases of 1.0 to deliver our first reference app to the community as well. That will allow developers to see how all the components fit together and how they can be used. That can be used as somewhat of a tutorial to get used to the new technology. And then finally we'll be organizing all of these components, these separate repositories, separate libraries, into an SDK that can be simply consumed by new developers to the community. I think the reality is existing developers are familiar with our quirks and how things might be separated, how we named things in the past, but to attract new developers we want to make sure that we have a tightly coupled SDK for them to download and start to use. That SDK will probably not be available until the release of 1.0, but the components will be, and they'll be a public shortly. Q: Has DashCore formally applied to be listed on Coinbase either through direct communication or their web portal? (name3) A (Ryan): Coinbase created an application process for coins and tokens to be listed on their platform. It is a very robust set of information that needs to be submitted, and I can confirm that Dash Core Group has submitted an application on behalf of the Dash network in its entirety. I believe that we have addressed every question that is on that questionnaire. As a matter of policy, we don't discuss the status of discussions or the likelihood of integrations. That's a policy that we follow across the board because we found that it affects our ability to be integrated if we're sharing information others are not comfortable with. So we can't comment further on it. What I would say to the community is if you want to see Dash integrated into Coinbase, let them know! I think they will respond to demand from their customer base to add specific currencies. If we have further information to share we will absolutely share it. Q: Will DCG be helping with integration partner testing for POS solutions that support Dash? So merchants can make a smooth transition allowing them to the ability to accept Dashpay username payments in sync with Evolution public launch? (Mark Mason) A (Bob): We definitely want to help our integration partners, and then they would be working directly with the merchants, for example, in a point-of-sale solution. So we'll do the best we can with the resources we have right now. Our integrations team is really set up to do that. That's a pretty lean team, but we're here to help and then I think we can also make sure that we have as many self-service resources available through the developer forums, the new developer portal and the new website. And then it's really a call to the community, both online as well as on the streets, to make sure that adoption is understood and the abilities are out there. Of course lastly we can always leverage our product team, marketing teams and tech support to put together good materials and make those available to the community. So we definitely want to help our integration partners, it will be a bit lean and strapped, but part of this is going to be train-the-trainer, building some expertise in the community, and then let the community help manage itself and manage our way through adoption. Q: Can Fernando reveal the results of the Dash Core Group $1.5+ million USD funded proposals for a 6 month digital marketing campaign in 2018? How was the money spent and where are the results? Did this even happen? The 2 proposals I'm referencing are below. One was an extension. (GA-mno) A (Fernando): We only did the campaign in the first proposal. It had to be delayed because Facebook banned crypto ads when we were about to launch. We redid the campaign for the Google platform and launched there in April. There are details about the results in the forum: https://www.dash.org/forum/threads/advertising-proposals.40044/ Basically we achieved some brand awareness improvements, increased downloads and there are a few more metrics that you can check there. However, when we launched on Google, Google announced they were also banning crypto ads. It was delayed for a couple of months, so it didn't affect our campaign, but it was clear by then that the environment for digital marketing in crypto was getting much tougher. Also, the price was decreasing significantly in the market, and we didn't consider it prudent to accelerate spending of the money, because we didn't know when we would get new funds. So in the summer we did a proposal to merge the marketing budget with the travel and conferences budget so we could pay for other obligations that were not yet funded and needed to go back to the network for money. That proposal for merging was approved, and the funds for the second proposal were mostly used to pay for Money 20/20, for translations, travel expenses, website development and a few other smaller things. It's worth noting that the funds were not as much as they were at the time they were received for the reasons that Glenn stated before. By the time the funds were converted to fiat, the amount was significantly less. We still have some of those funds - most of the marketing budget seen in the balance sheet comes from that, together with a smaller proposal back in the year for travel expenses. Now everything is together in one budget. Q: What pieces of Evo MVP are still missing after the release of 0.14? (fuzzyduck) A (Bob): That's a great question! Release 0.14 of core (dashd) will have pretty much all the features needed to support Evolution with the exception of blockchain username transactions. The bulk of what is missing is really not part of core, but what we're calling all of our layer two components: (1) the protocol for the Dash platform, which you may see references to as Dash Platform Protocol, or DPP. It will also consist of (2) the data and object storage mechanism, which we have been calling Dash Drive. And finally (3) the data access mechanism through our decentralized API, or DAPI. So this is why for core, version 0.13 and 0.14 releases are so important. Version 0.13 is critical because of the introduction of special transactions, since blockchain user names will become part of the special transactions. And version 0.14 is so critical because it implements the Long Living Masternode Quorums, which will facilitate consensus on those layer 2 objects in a manner that also supports HTTP access to the Dash blockchain enabled apps that will be built on that. The bulk of the work is in 0.13 and 0.14 with the exception of blockchain usernames. It's a good question and we'll continue to clarify that as we get closer.