\n\n
- Q: Are all devs now working on 0.14, or is there also progress made on v1.0 like usernames on blockchains, GUI etc? (fuzzyduck)<\/b>\n
A (Bob): It’s really a mix. We’re not working in a sequential manner, we’re definitely working in parallel. The core team is primarily wrapped up on 0.14, but the Dash platform team, which includes all the great development work on Dash Drive or the Layer 2 storage and the DAPI API, all of that is is 100% devoted to 1.0 development. Then across the wallet teams, it’s really a split. We have two wallet teams: one is entirely working on 1.0 and the other team has kind of split doing the version 0.14 enhancements, as well as working on 1.0. So it’s a good split right now. I think if the question was being asked to ensure that we were not working sequentially and waiting till we got completed work on 0.14 before we started work on 1.0, you can rest assured that there is quite a bit of work that’s going on. I’ll just re-emphasize that we did open up the repos that had been private prior to that, so it’d be easier for the community to be aware of the team’s work as well. So if you haven’t had a chance to look at those at the level of technical detail that you like, please jump on GitHub and you’ll see the work that’s being done in those repositories.<\/li>\n
- Q: Does the newly released\u00a0Crypto Token Guidance<\/a>\u00a0from the SEC offer any clarity for the expected status of the no-action letter? (Foxtrot)\u00a0<\/b>\n
A (Ryan): The newly released Crypto Token Guidance from the SEC is not substantively different than the information that Dash Core Group already provided to the SEC. The director of the SEC\u2019s Division of Corporation Finance, William Hinman, gave a speech on June 14th, 2018 which outlined a set of factors the SEC would consider in determining the security status of digital assets. This framework was codified by the Blockchain Association in January, which has come to be known as the Hinman Test. The Hinman Test was well-understood prior to our engagement with the SEC, and we included a legal analysis against the factors from Hinman\u2019s speech within our submissions to the SEC. Those factors address elements beyond the Howey Test, which was prior to the advent of digital assets, the measure of whether something was a security. Therefore, the recent Crypto Token Guidance is nothing more than a repackaging of the Hinman Factors, and there are no additional topics that resulted from its publishing that we feel need to be addressed, and we communicated as such to the SEC. I think that there’s really nothing new there other than the fact that it organizes it perhaps a bit better than it was given in a speech in verbal format.<\/li>\n
- Q: In June it is expected that the G-20 countries will meet and can dictate a global agreement about cryptocurrencies. What is the current status of the agreement with Coinfirm signed in 2016? about KYC\/AML for institutional. (BlockChainTech)<\/b>\n
A (Ryan): Coinfirm remains a close partner, providing compliance services to exchanges, banks, and money services businesses. We continue to introduce them to new exchanges and vice versa. In addition to Coinfirm, we also work with BlockchainIntel, which is another platform offering compliance services to the Dash ecosystem.<\/p>\n
So exchanges have a choice in provider for those services, and we’re in discussions with additional potential service providers that have expressed an interest in supporting Dash. Our ecosystem of KYL\/AML providers that exchanges need in order to meet compliance standards is expanding, and I think that gives those exchanges more choice. What we don’t want to have happen is have exchanges not even realizing that we have those options available, then being approached by a regulator about their compliance and making the decision to shut off Dash deposits, or Dash services. We have had that happen, and in that case we reach out ask them why Dash was delisted, and usually within a week, we’re able to get them back up and running. So this is something we’re on the lookout for, and we are proactively beginning to communicate with exchanges about these available options and ask them: “What is your plan for compliance if regulators require you to have this service? Do you know that we have these options available?” Because by providing that information to them, it can avoid Dash services being being removed and the services that are available do allow them to comply. So there’s no reason for an exchange to ever need to shut off services for Dash if regulators express concern about their compliance standards across different coins.<\/li>\n
- Q: Once we have Dash Drive, will we store the DAO Trust Election Results on Drive? (dashameter)<\/b>\n
A (Bob): The answer is: we can! Because that is the purpose, to extend the blockchain and build distributed apps on top of it. I would consider that to be a great project request. What we built to service the first election was something we didn’t have the capacity or the capability to do in that way at that point in time. I think what we should do is put that on our list of potential development projects which can have an appropriate priority, and we can then talk about different implementation approaches and whether that’s something that we want to pick up and what the benefits are. We have discussed it around the team, and architecturally it’s quite feasible on Layer 2 as it is on Layer 1. There’s some different approaches that you could take with it. It would be a fun project to take on, and we’ll have to see how it fits in with all the other priorities.<\/li>\n
- Q: There have been agreements with the Arizona’s University that the treasury has financed. It is known that there are problems to find developers or mathematicians in blockchain. Is there a plan to recruit talented students to incorporate them as scholarship or developers within the DCG team? (BlockChainTech)<\/b>\n
A (Ryan): We have had the opportunity to use multiple students from Arizona State University and continue to work closely with their blockchain group. As opportunities arise, we will definitely look to them as a recruiting source. To be clear, we are in a hiring freeze right now, so we don’t plan to fill any roles immediately, but that option is available to us. We worked directly with students last summer on our graphene research project and the team was excellent. The project ended at the end of last summer, and we haven\u2019t had funds for additional projects over the past school year. We are meeting with the University later today to discuss whether there is mutual interest in any additional research topics that we might be able to propose to the network.<\/p>\n
We will keep the abreast of those conversations as they develop, and if we feel that there is a good opportunity to continue collaborating with the University on research topics, we’ll bring that to the network. It really is a great resource for us, the reason being we could never conduct this research for the costs that are involved on our own. Arizona State University already has a large server farm that they can run simulations in. We couldn’t afford to acquire that type of resource on our own, and when we put research dollars in, those research dollars are matched from federal funding and other sources within the university to stretch our dollar. So if there are ways that we can use an investment in a grant in order to access all of those resources at a fraction of the cost, it really does a great benefit to us and it does a great benefit to ASU as well. Because when we contribute towards one of the projects or topics that they’re already interested in, it just makes it more feasible for them to be able to conduct that research. So they rely on multiple funding sources, our funding does allow us to kind of steer the conversation a bit towards things that are mutually of interest to us, so it is a great partnership for both sides in my opinion. I’m sure there are some topics that are worthwhile bringing to the network for a decision, and we’ll work to do that.<\/li>\n<\/ol>\n
<\/div>\n<\/blockquote>\n<\/article>\n<\/div>\n\n\n<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"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…","protected":false},"author":5,"featured_media":23938,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":"","_links_to":"","_links_to_target":""},"categories":[216],"tags":[],"class_list":["post-23937","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news"],"acf":[],"yoast_head":"\nDash Community Q&A - April 2019 - Dash<\/title>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\t\n\t\n\t\n\n\n\n\n\n\t\n\t\n\t\n