Dash cryptocurrency: How Moocowmoo’s alleged exit scam could destroy Dash

Posted: 4 December 2019 3:37 pm

Picture not described

Can Dash Core Group weather the allegedly impending storm?

Update 13/12/2019: Some Dash users are reportedly saying that Moocowmoo has resurfaced, and that they are getting their money back. The piece appears below as originally published, with two changes; the addition of the word "former" in the first sentence and the addition of one more cow-related pun.

According to users on Dash forums, former Dash core developer and masternode operator Moocowmoo (presumably not their real name) stopped paying out earnings from the Dash shared masternode service in August 2019 but said all user funds would be returned within a couple of weeks.

That didn't happen. Instead, Moocowmoo hoofed it to greener pastures, and anyone who was grazed by the incident started describing it as an apparent exit scam. Over the next few months, affected Dash users stopped chewing their cud and started organising.

When users took the issue to Dash Core Group (DCG Inc.), the commercial for-profit company that develops the Dash cryptocurrency, director of communications Philipp Engelhorn simply said, rather cryptically, that "there is strength in numbers" before putting the complaint out to pasture.

Now Dash Core Group is herding references to its previous relationship with Moocowmoo to the abattoir.

Moocowmoo was listed as a senior advisor on the Dash website team page but was removed sometime between July and November, according to Internet archives.

Picture not described


And on the DashPay GitHub page, Dash Core Group member Leon White just downgraded Moocowmoo from "core developer" to "community member".

Picture not described


But given Moocowmoo's long and prominent history as a Dash Core Group team member, there are obviously a lot of traces left to scrub, especially on the forums where people have been recommending Moocowmoo's masternode service for years now, largely on the basis of them being a Dash core team member.

The following exchange between two Dash community members aged extremely well.

Picture not described


For the sake of fairness, and context, it's worth noting that Moocowmoo has a history of making sporadic payouts and many previous fears of exit scams have turned out to just be false alarms.

And while it's too soon to speculate on what happens next, if you have to, there's one very plausible scenario where this is the end of the venerable (est. 2014) Dash cryptocurrency as we know it.

Opinion: How this could plausibly be the end of Dash

Dash Core Group (DCG) as a legal entity is a for-profit business, according to Crunchbase.

Based on publicly available information, DCG employed an individual by the name of Moocowmoo. Many Dash Core Group customers have alleged that they were defrauded by Mr or Mrs Moo while Moo was an employee of DCG.

There is evidence suggesting that victims only entrusted their money to Moo in exchange for a masternode service because Moo was a DCG employee and because Moo was offering a supposedly trustworthy masternode service in their capacity as a DCG employee.

A reasonable person could have been led to believe that the masternode service was being provided by DCG. If it wasn't a DCG service, the company should have made it clear that the masternode service was not provided by DCG, that it was actually just the "side hustle" of a DCG employee and that it in no way guarantees or endorses the service provided by Moocowmoo.

But it didn't. On the contrary, it actively advertised Moo's masternode service to customers. Moo then used their position of trust, and position as a representative of the DCG company, to allegedly abscond with customer funds.

When customers complained to DCG, its customer service was completely unhelpful.

Perhaps DCG ran through this same line of reasoning, which would help explain why it's now trying to scrub references to Moo as a Dash Core Group team member.

Customers are now talking about suing someone to get their money back, and there are two parties they could sue.

One of them is a mysterious, pseudonymous, uncontactable bovine who dropped off the grid months ago.

The other is DCG, a for-profit commercial entity registered in Phoenix Arizona with about a million dollars in the bank and $882,000 in revenue as of May 2019. It's hardly in a position to fight a lawsuit or refund all affected users. But if you were an affected user and you just wanted your money back, what would you do?

What's the damage?

You need to have 1,000 DASH, currently valued at US$50,000, to own a Dash masternode, and Moo offered two kinds of masternode service.

One was full hosting where people with 1,000 DASH paid Moo $35 a month (in DASH) to host the node on their behalf. In this case, people would retain access to their own funds, but they probably aren't going to get their $35 a month refunded.

The other service, which is where all the affected users come from, is shared masternode hosting. Here, users pool their funds to add up to 1,000 DASH and share the masternode earnings proportionally to their contribution. People directly send Moocowmoo their money, and Moo keeps track of who owns and is owed how much.

There are 4,843 Dash masternodes in operation, which currently lock up about $245 million of DASH. If only 20 masternodes (0.4% of the total) are shared masternodes under Moo's control, the total amount of money allegedly lost here is more than DCG can reimburse.

The problem with masternodes

One way this incident could spell the end of Dash is through a lawsuit that DCG can't afford to fight. Another way is through the realisation that its masternode system is flawed.

These masternodes are essentially high-powered nodes that act as trusted operators on the network, earning 45% of Dash block rewards in the process. Basically, by having these points of trust in the network, you can lean on them to access useful features such as instant transactions (a trusted masternode signs off on it, rather than the whole network) and a primitive level of privacy through CoinJoins, where a masternode can still identify users but a casual observers can't.

The whole point of masternodes is that they are trusted anchors of the network. But as this incident clearly shows, they can't be trusted.

Also watch

Disclosure: The author holds BNB and BTC at the time of writing.

Disclaimer: This information should not be interpreted as an endorsement of cryptocurrency or any specific provider, service or offering. It is not a recommendation to trade. Cryptocurrencies are speculative, complex and involve significant risks – they are highly volatile and sensitive to secondary activity. Performance is unpredictable and past performance is no guarantee of future performance. Consider your own circumstances, and obtain your own advice, before relying on this information. You should also verify the nature of any product or service (including its legal status and relevant regulatory requirements) and consult the relevant Regulators' websites before making any decision. Finder, or the author, may have holdings in the cryptocurrencies discussed.

Latest cryptocurrency news

Picture: Shutterstock

Get into cryptocurrency

Ask an Expert

You are about to post a question on finder.com.au:

  • Do not enter personal information (eg. surname, phone number, bank details) as your question will be made public
  • finder.com.au is a financial comparison and information service, not a bank or product provider
  • We cannot provide you with personal advice or recommendations
  • Your answer might already be waiting – check previous questions below to see if yours has already been asked

Finder only provides general advice and factual information, so consider your own circumstances, or seek advice before you decide to act on our content. By submitting a question, you're accepting our Terms of Use, Disclaimer & Privacy Policy and Privacy & Cookies Policy.
Go to site