How can I help?

I am in Asia. Can a testnet be made with me?

Don't get me wrong I have contributed in the past to this community. I actually also mined a fair amount of DMDs in V2 and V3 which I still have in my wallet. I also helped at that time building a MAC wallet from source.

7 years have past since then, but I have seen no improvement in terms of growth, quite the opposite in fact. Yes price has increased but that is somewhat artificial considering the low volumes and market cap of the coin.

At this stage DMD should already be trading in far bigger platforms than the current ones considering its maturity.

This coin needs to be exposed to a wider audience and in bigger trading platforms else it will die like thousand others have already. It would be a shame though. This is not only the responsibility of the community as a whole as it is often uni-directionally reminded in this thread but also of the funding members and developers who should push the coin as well for wider adoption. I understand this cannot be forced but at present it's not being traded in any significant platform and that's a major drawback. The only platforms trading the coin are tiny ones and nothing moves.

Hopefully the founding members will make a move after the v4 transition else I don't this going anywhere.

This coin is still dead. Regrets is all I have for having mined this. 

It wasn't a mix up. I simply installed V3 using the V2 folder. Anyway it's all resolved now. Thank you.

I am trading on Bitkub and Binance. Any chance DMD will be added in those platforms?

hahahah yes I meant I deleted all exept those three!!
Another question though. blk0001.dat and blkindex.dat have not be recreated. Is that ok?

Yes I am on block 819547. I did as suggested. Deleted wallet.dat blocks and chainstate directories.

Now working like a charm.

Thank you.

a v2 wallet.dat should not be used with a v3 wallet

export the private keys that hold coins and import them into a new v3 wallet

[/quote]

This  seems to have made the trick. However I still get the "Synchonizing sorks". It's been stuck there for a long time although the blockchain is up to date.

I didn't find anything referring to this in the FAQs.

Thanks.

And the sync also seems stuck after the blockchain was udated:

Hello. Old timer here. Decided to open my wallet after many years. Updated to V3. Now each time I open the app I get this:

I can see all my DMDs but this error message is annoying. What can I do?

I've learnt my lesson in the past. Do not use Remote Desktop! Most other options will do, although I prefer Teamviewer.

BTW, I asked this question before but got no answer. Will algo M7 be added to your releases of ccminer and possibly optimised?

at +200 + 400 some of my cards end up crashing. This is too much OC for me.

Just updated to v 1.5.5.

NICE updates. Integrating the miner output to Miner Control makes things easier. I have a comment though. When I move the cursor inside the output windows, the cursor disappears. In fact the cursor turns black and with the black background it becomes invisible.

Thanks SP_. In fact I already have Nicehash control tool. Forgot I had it Will use that, thanks.

Release 11 of ccminer is crashing by itself. Lost all night of mining. Reverting to DJM34's release of ccminer.

It looks like the ostrich putting its head in the ground technic to avoid looking at the problem...

It does it with me 4 out of 5 times:



Then pressing Y or N produces the same result: ccminer closes

I never EVER had this problem with DJM34's release.

I am referring to SP_'s release 11 of ccminer. I know the devs who contributed to ccminer... Thanks for the lesson though
DJM34 was the latest dev to have worked and produced a stable release with significant improvements. FYI the very latest improvement of ccminer was done by SP_ (~ +200 Khash) - Still beta as I understand it though.

In order to quit ccminer you can proceed by pressing Ctrl+c. In SP_'s release of ccminer there seems to be a bug where Ctrl+c will lead to the crashing of ccminer.