Can you provide any more info about your system? Windows 7? Windows 10?
The wallet has built in sync nodes so it should sync up by itself as long as there is a working internet connection. Do you have a firewall blocking the MUE client?

Normally it takes a matter of minutes to sync up the wallet.

A thumbs up for the humoristic and easy to grasp bus article! On to the Dash express we go

A masternode requires 500 000 MUE as collateral, and has about a 20% yearly payback in MUE. The current yearly packback in USD, is about $9500. We do however anticipate the USD returns to increase.

Thanks for the idea raoulsergia, we can take a look and see what they say.

Forgot to say that it can take 24-48h to get that cleared, but it usually gets sorted out with their support.

A general piece of information mates, all QUARK-based MUE coins mined after the cutoff date of June 25 2017 will not be swapped to new MUE-X11 coins. We will have to do some block chain analysis to verify the coins, and manually verify the swapped coins where there are needs to do so.

If you are successful in getting your coins out of Cryptopia, the coins could be "tainted" with newer mined coins, so you will not be able to do the swap 1:1.

This is just a heads up, if the coins are on an exchange, and they have been taking deposits after the cut-off date.. well a user could very well end up with newer coins that cannot be swapped. It is impossible to know before hand for the user, however, the auto-swapping system does the work of verifying the coins. The exchanges who did not want to participate in the first and now second swap, and kept on taking deposits for old non-valid tokens, will have to deal with their angry customers.

Great work Core team and testers! Thank you all for your countless efforts in bringing us a much improved Dash client

Maybe consider running a Linux VPS node as your hot wallet, then you can close the windows cold node and leave it closed. From my experience, Linux has a far better memory management then Windows anyway.

Have you setup your local masternode.conf, because it looks like you might have a bitcloud.conf and masternode.conf running the masternode off your hot node on the VPS?

Seems kind of strange that your local wallet wouldn't know about your masternode unless your local masternode.conf file is empty?

It means that you have not specified you rmasternode collateral correctly.
User darkomega69 is right when writing:


Check the instructions again. Once you changed your collateral amount and made a new transaction, the collateral specification needs to be updated on both your hot node and the local wallet.
Your output from the hot node (VPS) shows that it was all synced and ready, waiting for instructions from your local (cold node) wallet.
However, you most likely need to fix the collateral settings on both nodes, let them sync again, and once ready, issue the masternode start command from your cold wallet.
Good Luck!

What was the output from the commands posted above? They can help you pin down the problems with your masternode.
4) What does give you?
5) On the VPS, what does say?

I cant give too much help about Bitcloud, but what have you done to check your masternode?

1) Verified that your client is all synced up?
2) Verified that your hot node is ok?
3) Is your node present in the masternode list?
4) What does give you?
5) On the VPS, what does say?

It's hard for others to help you mate unless you can give any info on your setup, what you have done to check things etc etc...

You would need to setup an second VPS, make a new transaction for the collateral, generate a new masternode key (genkey), adjust your second bitcloud.conf and masternode.conf.... and that's pretty much all there is to it.

So you run a VPS per masternode and you can control them all from the same cold wallet.

Yes it is technically possible, but in practice, not for the average user, because you have to setup your own stratum/gbt proxy.
Better to just join the official weminemue.com mining pool which has 0% fee anyway, and it "just works" 

Sure! running on 16.04 works fine, I wouldn't know about running the provided binaries on 16.04, but compile yourself and the client/daemon should work OK.

Hey Virtuoso, yeah MUE took a hit but is already on its way up a bit. The team is still working hard in the background and are working on the upcoming client release. We are looking at getting the self funding/budgeting all working, several projects to be announced later and MUE will be presenting and sponsoring the crypto-conference in Birmingham, UK http://bitbrum.org/

So lots of activities in the background. We are more of a "work hard and deliver when ready" kind of group rather than pre-announce things "ICO-style".

The price is still low, so either mine or buy, whatever rocks your boat!

I concur, they are probably many of the older holders following here. Personally I find it easier to read up on the news being published here by the devs and Dash Force team as I cannot follow all of whats happening over in the new Discord channel. Since I am a BTCtalk regular it helps to keep a tab open for our beloved Dash thread

The trolls come and go, but they help in their own peculiar way.

You could try checking the date for the payouts, the listing is a bit broken so the payments are most likely there. You could try searching for a payment in October and you will be able to see the payout.

Otherwise jump on to the MUE slack and try to get a hold of user @pjcltd or pjcltd here on the BTCtalk forums.

Thanks BHTeam, the site looks nice! A clean interface and helpful stats. 

Looking great CoinFolium! Any plans of getting your app on the IOS AppStore as well?