Questions answered during the Dash Core Group quarterly call have been (automatically) transcribed below:
Questions answered during the quarterly call have been (automatically) transcribed below:
- Q: As we move from build to launch of 1.0, how does DCG plan to support the go-to-market (of DashPay specifically)? Core team product marketing hires? Partnering with an external agency? (craigwrong)
A (Fernando): As we know and, and as Bob has detailed previously, DashPay is one of the two parts of what we have always called “Evolution” that we’ll be launching soon, the other part being Dash Platform. Both go together, and in fact Dash Platform is a prerequisite for DashPay to work. Dash Platform will be on testnet in late 2019, and DashPay will arrive sometime in 2020 once that is working well. So both launches go together. In the case of DashPay, we are working on a plan that includes our own channels, the community and some extra PR effort. This plan would require very little money and it’s limited by definition. On top of that, we’re working on different pieces to add that would require extra funds that we would need to request from the network when the time comes. In September, as Ryan mentioned before, we would go through a call to discuss marketing with those interested and get some feedback on those pieces and also new ideas the community may have to introduce in the plan. We are exploring promotions, some ads, some events, but as I said these will all depend on the resources available because right now the full focus of the organization is putting the resources towards software delivery and the marketing activities of the reduced budget. Even the base plan we are working out there to get into the community and our own channels could get significant results. Not everything needs to be paid.
- Q: What has been happening with Shift PR since the DAO voted to change PR company, and what can we expect from them? (krish)
Q: I think our new PR firm, in combination with Core, needs to come up with a better plan and be very transparent about that plan to the community. (…) Are there objective metrics that we use to evaluate the performance of our Public Relations? (solarguy)
Q: Will there be any targeted focus to Shift’s PR efforts regarding regions in which Dash has made good progress? And will they be reaching out to POs in those regions to coordinate such targeted efforts? (agnewpickens)
A (Fernando): The contract with Shift was signed in May, so the first full month they worked was June, so we are a bit over two months into the contract. In these two months, they have supported DCG in five public announcements, including Aircoins, blogs together, ChainLocks activation and Travala. Those resulted in around 37 pieces in different outlets. They are reporting and giving all details to Dash Watch, and they will publish video with them, so any details and anything you want to confirm can be checked with them. They’ve also work with us in updating the Dash messaging. Basically there’s small things there in certain places. They’ve also built speaking and award structure that could bring in the future some more media attention. And finally they supported DCG on crisis management when it affects communication. There’s couple incidents we’ve had where they’ve been around giving us advice. That’s basically what they do. These parts, and pitching to journalists and supporting us in these other roles for messaging and crisis. They do not produce their own content like most PR firms don’t do. That’s very important to clear up, because sometimes I’ve seen people saying “why dont’t they write a piece here or there?”. They they work in influencing others.
On the second part of the question, the current PR firm is focused on the English speaking market, because that’s where the biggest media outlets are. This doesn’t mean that the news from (for example) Latin America doesn’t fit in there, in fact those are the ones that have been finding more traction. So that’s important to take into consideration. Regarding the other proposal owners, they are all welcome to reach out to Michael Seitz, our marketing manager. He coordinates with other proposal owners announcements that could be of interest to media so they can go through Shift. There’s already a working group that includes Dash Nation, DACH, Dash Thailand and Dash Nigeria that work with him in coordinating both PR efforts and some business development, so they work together better. Michael will be happy to accomodate with Shift’s capacities. In the future, we would like to expand and do more focused PR efforts in Latin America. We explored that a few months ago and have some new market funds for that. But we found the market was fragmented and it ended up being expensive and we didn’t have the resources to do that at the point in time. But we still have that idea in mind, and we still talk with companies. As we advance in those conversations, I think we will be able to do more things in Latin America in 2019, with Shift or some other company.
- Q: […] What are the main pain points that currently hinder Dash from being considered a ‘Blue Chip’ crypto, with the obvious factors being the SEC no-action letter, and also their unwillingness to support a network that exhibits privacy features… What may need to be accomplished in order to give Dash the green light for institutional investment going forward? (Foxtrot)
A (Ryan): The primary efforts that we put in over the last year have centered around our status as a security and the impact of PrivateSend. I think that the work with the SEC has yielded what we needed from it. Prior to engaging with the SEC, the SEC had been reaching out to exchanges, and exchanges were in turn reaching out to us with concerns about our status as a security. We engaged the SEC, we actually traveled to DC, Glenn Austin and myself, and met with multiple agencies within the SEC or multiple departments within the SEC, answered some follow-up questions and since then we have not heard of a single inquiry. I don’t think that it’s realistic to expect them to issue a no-action letter. They haven’t done it for any projects except for one I believe at this point, and that one was essentially a digital coupon that was so clearly not a security that that they felt comfortable doing that. I think what’s more important is that it seems from what my observations are that they seem satisfied with the answers that we gave. I think that the SEC was a potential concern for us at one point in time. I don’t think it’s a concern any longer. When we share our legal arguments with any particular exchange, they are very convinced within their compliance departments. I think across the board there’s widespread consensus in the industry that Dash is not a security.
As far as the PrivateSend issue, I think we took a big step forward today in addressing that. There’s much work to be done beyond obviously developing the position paper and performing PrivateSend transactions on Bitcoin’s blockchain to demonstrate that these protocols or sets of rules that underpin transactions are identical. We now need to educate, and so we’re gonna be taking that document as well as the overall legal argument and doing personal outreach with regulators, influencers, consultants and compliance departments in order to spread that information and answer any questions. I think are our argument is very very strong. The feedback that I’ve seen so far on that document is that it is quite useful. I want to make clear that that does not mean that we don’t have a commitment to privacy – we do, and we continue to have a commitment to privacy. What we’re arguing here is that there is no legally definable reason why Dash should be held to a higher standard or held to different requirements than Bitcoin. I think if you read that through that document you can see the strength of our argument and we hope that that point of view can begin to resonate within the industry. Particularly in markets where there’s already been some type of action. The only one I’m aware of is in Japan, and we plan to address that with JFSA (the Japanese Financial Services Agency) in order to demonstrate to them that there is no legal reason for why we should be treated any differently in that market. I think that we’ve effectively used that argument already with European regulators. An example here was with eToro. eToro was approached by their regulator, they approached us. We were able to arm them with this information and they were able to address regulator concerns. So I think this is a very addressable set of issues and it mostly focuses on education. People have uninformed opinions about Dash, or they simply are looking at a list of cryptocurrencies with privacy features without drawing any distinction between how those are implemented and whether or not exchanges can meet stringent compliance requirements with those currencies. This is this is going to be a substantial effort on our part, but I think it’s important to ensure that we continue to have access to trading pairs and access to the traditional financial system. So we’ve we’ve really put some priority behind this.
- Q: What integrations with stock exchanges are taking place? Bitcoin Cash is trading on the Swiss exchange, can Dash Core also pursue those types of integrations? (dancefordistribution)
A (Ryan): Yes we can. In the case of the Swiss exchange, I’m aware that there is already one of Dash’s teams that is in conversations. Dash Core Group stands ready to support in whatever fashion we can, for example with the legal work that we’ve done or anything else that can be useful. Bitcoin Cash being listed on the Swiss exchange – I’m not sure on the details there. There were reports that Roger Ver personally funded that and that it may have cost seven ro eight figures in USD terms in order to achieve that listing. I’m not sure if those reports are accurate, but if those are the expectations it may be cost prohibitive to pursue an integration like that until a later date but we’ll see. I’m sure that with the groundwork that Bitcoin Cash laid, a lot of those hurdles may have already been overcome. So we’ll work on it and we’ll see where where those conversations lead.
- Q: Previous Evolution roadmap planning and reporting has noted a plan to eventually deploy trustless masternode shares to the network. Is this still planned? Since such a development would affect the basic economic incentives behind the network, will masternodes be given an opportunity to vote before development on this feature begins? (phil7)
Is anyone currently looking into some sort of protocol level implementation of trustless masternode collateral sharing or is it an abandoned idea and it’s left to trusted third parties to implement shared masternode solutions? (Dandy)
A (Bob): This has been discussed since the original engine for Evolution. It is in our backlog and but it has not been prioritized. Basically our backlog, we go through it and will prioritize items for upcoming releases. However it’s in there, it remains in there, we have not eliminated it. But according to the roadmap we laid out today it would not be expected anytime within the next couple of quarters. Obviously the strength of Dash comes partly through the community as well, and so trusted third parties who have solutions to implement would always be welcome. But it’s not lost on us it just hasn’t hit priority level of the other features that were rolling out right now.
- Q: What’s the plan of Dash to take advantage of the opportunities in Africa? (Nathaniel)
A (Ryan): I think the question intended here is what’s the plan of Dash Core Group to take advantage of the opportunities in Africa, hopefully I’m not distorting the intent of the question. I think that Africa, and I’ve stated this before, has a lot of high potential markets within it. We’ve seen that cryptocurrency adoption is stronger in markets with high inflation with a low degree of financial freedom and that certainly is the case in in quite a number of countries within Africa. So I think there’s a good fit there. In terms of Dash Core Group we have limited resources at the end of the day we have a business development team of two. So we have to prioritize where we think our efforts are best utilized. Venezuela is clearly a standout, and so in terms of geographic focus, if we have additional resources right now I think that that we would pursue that just in terms of priority. But I think that one of the strengths of our proposal system is that it allows other teams to have a go and try to see what can develop there. Ultimately if the opportunities start to open up in particular markets in Africa, it benefits all of us. So Dash Core Group for the time being until we have the ability and the resources to expand our business development team, we really have to concentrate on making sure that the strategies that we are pursuing are successful first, before we can start to really expand out and diversify our efforts. So it’s not that we don’t think Africa is a good opportunity, it’s just that in terms of priority we’re really focused on Venezuela at the moment.
- Q: Now that Coinbase has acknowledged on its own blog to explore support for Dash and 7 other cryptocurrencies, can we expect the secrecy to be lifted on this specific topic and can we expect more information about the possible internal communication so far between Coinbase and Dash?
A (Ryan): I partially addressed this question already, but let me expand on it a little. CoinBase got a good deal of public scrutiny after they listed Bitcoin Cash on their platform. There were accusations that there was insider trading, that there were people front running the listing, and there were internal investigations into it. I don’t think there were any public conclusions written about it. But what I can tell you is that I think CoinBase’s publicly facing communication changed substantially after that point in time. I think that their compliance department may have really attempted to address this issue. What it means for teams like us is that the communication tends to be very one-way with them relative to other exchanges. There are requests for information. There isn’t a great deal of information that comes back to us about what they’re thinking or what type of timing they might be looking at or whether they have specific ideas about whether they will integrate with us or not. Unfortunately there just isn’t a lot that we can share. We are responsive to them. We of course are providing any information that they request. We’re offering information that we think might be helpful to them in their assessment. But honestly I think that Dash Core Group will find out about whether or not Dash gets integrated at the same time as everybody else. I think that this is CoinBase’s mode of operations with all cryptocurrencies that they list. It’s frustrating for Dash Core Group, and I’m sure it’s frustrating for the community but I think this is just the way that they they operate. So all I can disclose really is that we’re communicating with them and replying to their requests but I don’t think that we will get a lot of feedback from them on how that is going, whether they would list us, when they would list us. So hopefully that sets the expectations here.
- Q: If there is a disagreement among DCG core team members about whether a pull request should be merged into the Dash code repository, how is the final decision made? Are the Dash Github administrator accounts legally owned/controlled by DCG (the entity), so that developers cannot go against a decision that was made from the aforementioned procedure? What about control over other assets of interest to the network such as Reddit (senior moderator is currently tungfa), is there an established hierarchy of control through DIF > DCG > DCG employees to ensure control ultimately lies with the network? (TroyDASH, Dash Crypto)
A (Ryan): I can talk about this from a couple of different perspectives. One is: keep in mind that many of these tools that we deal with require an individual account that has access to them as the senior moderator. That’s just the way that they’re built, we can’t change that other than you know ensuring that we have access to that account in a shared tool that stores passwords, and we do. A lot of these platforms don’t necessarily have multi-person access control built-in. Where where it does, we utilize it, but that’s not always the case. So recognize that we’re under constraints here, ultimately some of these things do have their own policies around logging in and having a single username and password associated with an account. But we are mindful of ensuring that we have multi-party access. In the case of the Dash code and when there’s disagreement there: there’s frequently disagreements, and we have processes by which we attempt to resolve those. Sometimes there’s deep-rooted differences of opinion that have more to do with an individual’s values than a logical argument can necessarily address. When those come up, it’s likely that those opinions would come up within the community as well. There was an incident that probably led to this question around how to use the proposal system to arrive at decisions with our PR agency. When those issues were arisen within the team, it’s far better for us to address them and come up with a solution than to ostracize someone. Because if we’re ostracizing someone’s opinion we’re doing it with the community as well. In this case, we saw a a path forward that involved just holding an additional vote in order to effectively have a runoff election if you will. The result is that everyone was on board with the final decision, and that’s a good thing. Ultimately we do at times run into issues where we do not have agreement on something, and ultimately there is some path forward. We’re all professionals and we have the ability to work together and come up with solutions that we can all live with. Like I said if there’s an issue within the team, likely there would be one within the community, so it behooves all of us to try our best to address them. Ultimately I think – Bob you can answer the question about the administrator rights and control – but I don’t think that there’s the ability to kind of hijack the repository in any way.
A (Bob): Nothing really to add there. This is software that’s used by all projects, we’re not in any unique situation. We do our best and obviously the code is available if there was major disagreement in the community, the code is there for everyone. But we’re just using the tools as everybody else has, if we’re missing the essence of the question, please feel free to add things on and we’ll do our best to answer.
- Q: Does DCG have any information regarding the stress test/spam attack that happened last night? Was this planned? Do we know what person or agency did it? (gerhard.hahnel)
A (Bob): What we know is that there was load experienced on the network during what I would call an “unofficial” stress test. We have a history of random stress tests that occur within the community but outside of the core group. For obvious reasons, if we were to perform any tests ourselves as a core group we would be doing that load testing on testnet. But it is available that anybody could stress test mainnet at any point in time. On many occasions we’ve been told in advance by community members that they would be performing one at a certain point in time. In this case, as far as I know we did not hear that in advance on this. So what I can tell you is what happened and what we’ve learned from that. What happened is we saw issues where mempool was being artificially filled up and maintained there for a short period of time. That had some impacts to the transactions that were going through, what was happening in the blocks. What we’ve learned were that some of the mining pools are still capped at one megabyte block sizes, likely due to custom implementations. Obviously if somebody is using our own dashd, it’s going to be two megabyte block sizes, but miners can have their own custom software on that, and that’s up to them if they choose to do that. So that was interesting to see.
Related is that we saw some of those pools were not emptying mempool, and so mempool was filling up. What they were doing was producing also near empty blocks. We’ve been in active communication with any pools that are in that situation. The transactions do appear to be spam (they they’re one input one output and very low fees associated with them) and so miners and mining algorithms have the opportunity and the right to determine what they accept as far as putting into a block. So we’ve seen that, and that’s been interesting. We’ve also seen that some of the masternodes have run out of storage space, causing them to crash. But we we think that that is as a result of the storage of InstantSend locks. We are now storing all InstantSend locks for all transactions, where in previous versions we had flushed those after seven days. We’re building in to address that, we’ve got a 0.14.0.3 maintenance release that will be coming out, that will remove those InstantSend locks that have occurred via ChainLock, and those will be removed after the lock is confirmed. So that will help out for any anybody experiencing those issues.
We’ve also seen some real small edge cases on masternode banning during quorum development with LLMQs where Masternodes can be banned. If they get banned at a certain time right on the brink of a new quorum becoming active, we also notice some issues there. These are the exact types of things we would want to observe, and expect to observe, in a stress test. So whenever one of these stress tests does occur, we are going to watch it closely observe it, and and make changes. Out of this one in particular we have two pull requests that had already been in the works that would address a couple of these cases, and that will be released in 0.14.0.3. But we don’t know who performed it. We would love to facilitate these on testnet to have less impact. The volume that was reached is not volume that we will ever reach organically for years to come literally. We appreciate the efforts of the parties that are doing this. It can be a little disruptive, or alarming as Ryan said before in key metrics. It skews all our metrics! So there are many reasons why a mainnet unofficial stress test is not desirable, but we’re always going to learn things, we’re always going to improve the protocol and we’re doing so in this situation as well.
- Q: Are there any plans for a future Dash conference event?
A (Fernando): There are plans. They are contingent on launch of Dash Platform and DashPay. Depending on when that happens, we are working on different alternatives. Ideally near some other big conference in terms of time so we can hijack their attendance. We will know more as the launch approaches and we have more certainty. Before that we are going to be hosting a couple of smaller events. This is mostly for community and partners in Europe and the US, probably in October. They are intended to provide more information on the launch of Dash Platform and DashPay. But because of that we will be waiting for some developer workshops that are going to happen in late September – early October. After that we will have more information and will make these smaller events in the US and Europe so we can share all the relevant information with the parties when we start the preparation for launch and involvement of everyone.
- Q: When will PrivateSend be available on any mobile wallet?
A (Ryan): I think that one of the challenges we’ve always had with PrivateSend on mobile is that it requires a connection throughout the process of forming the transactions, otherwise abandoned participants can cause PrivateSend mixes to fail. It’s always been a challenging problem. One of the things that we’ve done to help address that is by making transactions instant and making them instantly respendable. So chained InstantSend is a prerequisite to making PrivateSend mixing work on a mobile device. Our focus right now is certainly around preparing our wallets for the platform and for DashPay capabilities, as well as launching the platform itself. This is another backlog item that I think carries a good deal of support from the community and would rank pretty highly in terms of the types of features we’d like to incorporate in the future. So although you didn’t see that on the roadmap today, I would anticipate that this is a pretty highly relevant feature for a lot of people. I think that we will appropriately evaluate that as well as get an estimate of how much resources would be required to implement it, and appropriately prioritize that within our roadmap in the long term. I think this is very similar to that question that we got around trustless masternode collaterals. It’s in the backlog, we want to get to it and we have our focus right now on Evolution-related features.
Original link: https://www.dash.org/forum/threads/community-q-a-july-2019.47266/#post-215178